ci: require secrets.PYCLOUDLIB_TOML, add lxd_vm and ec2 scheduled jobs by blackboxsw · Pull Request #6715 · canonical/cloud-init

blackboxsw · 2026-02-05T05:17:17Z

Improve our public scheduled integration test coverage to cover lxd_vm and ec2 platforms.

Running integration tests will require 3 repository secrets PYCLOUDLIB_TOML_B64, SSH_PUBLIC_KEY and SSH_PRIVATE_KEY in order to configure pycloudlib to run integration tests.

This PR renames and orders Github workflow files to aid visibility when manually reviewing and running actions.

Add assertion on a non-empty Github repo-level secret named PYCLOUDLIB_TOML_B64 which will
be base64 decoded and written to a temporary file which is set in the environment variable PYCLOUDLIB_CONFIG. This config is used sa runtime integration test configuration for pycloudlib.

Add an assertion step in 20-dispatch-common.yml to error when
secrets.PYCLOUDLIB_TOML_B64 is absent and conditional logic which skips
each integration test step to avoid wasting runner cycles on integration tests.

Proposed Commit Message

See individual commits

Additional Context

Test Steps

Failed run example empty or absent secret PYCLOUDLIB_TOML_B64 https://github.com/blackboxsw/cloud-init/actions/runs/21699149948/job/62575866822

Success RUN with PYCLOUDLIB_TOML_B64 secret set to "[ec2]"
https://github.com/blackboxsw/cloud-init/actions/runs/24084983529/job/70255277685

Merge type

Squash merge using "Proposed Commit Message"
Rebase and merge unique commits. Requires commit messages per-commit each referencing the pull request number (#<PR_NUM>)

holmanb

first pass

holmanb · 2026-02-05T15:01:41Z

+          awk '/cloud-init version: /{printf DEB_VERSION=$NF; exit}' pytest-${{ inputs.platform }}-${{ inputs.release }}-${{ inputs.image_type }}.log
+          awk '/image-serial: /{printf IMAGE_SERIAL=$NF; exit}' pytest-${{ inputs.platform }}-${{ inputs.release }}-${{ inputs.image_type }}.log
+        shell: bash


What is are the awk commands doing here?

And why bash?

Ahh I was going to use these to help create a top-level report output that would announce what version of cloud-init was installed during the test. I'll drop this from this PR until I have a working approach. I didn't like how opaque our GH workflow runs are when compared to jenkins jobs which announce the version of cloud-init being tested.

I was originally stuffing env vars them into GITHUB_ENV per these docs and the ctrf.io step can extract and use the environment variables for report headers or summary.

blackboxsw · 2026-02-11T23:26:40Z

        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd  # v6.0.2
      - name: Setup LXD
+        if: ${{ env.REQUIRED_SECRET != '' and contains(fromJSON('["lxd_vm", "lxd_container"]'), env.CLOUD_INIT_PLATFORM ) }}


Avoid the setup-lxd step if we are not on CLOUD_INIT_OS_PLATFORM lxd_container of lxd_vm.

holmanb · 2026-02-19T15:02:04Z

+          test '${{ secrets.PYCLOUDLIB_TOML }}' != '' || echo "ERROR: Missing required repo secrets.PYCLOUDLIB_TOML non-empty value."
+          test '${{ secrets.PYCLOUDLIB_TOML }}' == '' && exit 1


This checks for the same thing twice, I think an if / else would be cleaner

Done. We only really care to exit 1 in the face of no secrets.PYCLOUDLIB_TOML or empty string. So, I just put the operation in a single if clause.

holmanb · 2026-02-19T15:05:20Z

      - name: Checkout
+        if: ${{ env.REQUIRED_SECRET != '' }}


Since env.REQUIRED_SECRET is assigned from secrets.PYCLOUDLIB_TOML, and the first step has an exit 1 when secrets.PYCLOUDLIB_TOML is empty, is this not redundant?

Same comment elsewhere.

Dropped all unneessary conditionals checks. An exit 1 above will prevent running these steps anyway.

holmanb · 2026-03-16T14:37:39Z

@blackboxsw let me know when this is ready for re-review

holmanb

A few comments.

holmanb · 2026-04-06T22:42:16Z

@@ -0,0 +1,13 @@
+name: "Daily: Integration Resolute lxd_vm"


The naming scheme isn't going to work with future expansion of new series, additional platforms, etc.

I would prefer that we do it in a way that isn't going to force us to do the same thing again the next time we add more platforms - something a little bit more sustainable would be better.

Also - numbers simultaneously increasing and decreasing is chaotic.

I have dropped all unrelated renames and moved all integration platform runs to the end of the ordered list. Each platform is now grouped and reserves 10 workflow test slots for each platform.
Platform group prefix will be the following for each platform:

100: lxd_container

110: lxd_vm

120: ec2

The oldest tested series (22.04) will be the first index at prefix 100-. Each additional supported series will increment from that initial platform index:

XX0: 22.04

XX1: 24.04

XX2: 25.10

XX3: 26.04

Successful GH run after renames

blackboxsw · 2026-04-07T14:11:52Z

@holmanb I have updated this branch and linked a successful runs on Ec2.

Rename the reusable dispatch workflow to 100-dispatch-common.yml to establish a convention where 1xx = reusable/callable workflows. Workflow indexes 11x/12x/13x are caller workflows grouped by platform: lxd_container, lxd_vm and ec2. Move scheduled daily-integration-*-lxd-container.yml files to 11x-daily-integration-*-lxd_container.yml equivalent. Each platform group of scheduled workflows will be ordered by increasing Ubuntu series: 22.04, 24.04, 25.10, 26.04.

…er temp - Declare PYCLOUDLIB_TOML, SSH_PRIVATE_KEY, and SSH_PUBLIC_KEY as required secrets on the workflow_call trigger. - Add an early assertion step that exits immediately if PYCLOUDLIB_TOML is empty. - Replace the ssh-keygen throwaway key with a new 'Setup SSH' step that writes the injected public/private key pair to ~/.ssh, for use in authentication to instances under test - base64-decode PYCLOUDLIB_TOML secret and write it to $RUNNER_TEMP/pycloudlib.toml to keep secrets off the persistent filesystem. Add cleanup to remove the file unconditionally on exit.

Add workflow files 120-123 for lxd_vm, daily, on all supported releases. Add workflow files 130-133 for EC2, twice weekly, all supported releases All new caller workflows expose an install_source workflow_dispatch input, defaulting to ppa:cloud-init-dev/daily, and forward the three required secrets to the common dispatch workflow.

Avoid dependency on ctrf.io integrations and shift to pytest-json-ctrf for report formatting needs. - Add pytest-json-ctrf to integration-requirements.txt; this plugin writes a native CTRF JSON report file and provide --ctrf to pytest. - Set a descriptive title that includes platform, release, image_type, and install_source. Job and environment cleanup: - Move CLOUD_INIT_OS_IMAGE, CLOUD_INIT_OS_IMAGE_TYPE, CLOUD_INIT_CLOUD_INIT_SOURCE, and CLOUD_INIT_LOCAL_LOG_PATH from the job-level env block into the 'Run integration Tests' step env, keeping the job env focused on credentials and config that steps other than the test runner need. - Add a default of 'ppa:cloud-init-dev/daily' to the workflow_call install_source input so callers that omit it still get a sensible value. - Add install_source workflow_dispatch input with the same default to the lxd_container caller workflows (110-113) and pass it through.

blackboxsw · 2026-04-24T21:02:25Z

@holmanb I believe I have addressed all questions or suggestions. I have refactored the commits into logically separate commits for ease of review.

Final successful run https://github.com/blackboxsw/cloud-init/actions/runs/24911475438/job/72953869594.

Copilot

Pull request overview

Copilot reviewed 19 out of 19 changed files in this pull request and generated 5 comments.

holmanb · 2026-05-06T23:15:02Z

+    uses: ./.github/workflows/100-dispatch-common.yml
+    with:
+      release: resolute
+      platform: ec2


I see now that an issue in one of my latest comments was introduced by following one of the recommendations suggested here.

Please self-review for consistency with the existing code when applying suggested changes.

Given that we now decided below to shift this to a required parameter, all workflows will provide image_type for both cheduled and manual workflow dispatch.

blackboxsw · 2026-05-06T15:23:10Z

+        run: |
+          sh -c 'echo "${{ secrets.PYCLOUDLIB_TOML}}" | base64 -d > "$PYCLOUDLIB_CONFIG"'


We'll prefer to validate that the content is base64-encoded. Will perform this validation by checking for a non-empty decoded PYCLOUDLIB_CONFIG after processing.

After review, we'll allow the base64 -d failure and non-zero exit code leave us with an adequate breadcrumb to resolve this.

holmanb · 2026-05-06T23:17:14Z

+        options:
+        - generic
+        - minimal
+        required: false


I would have suggested making this required instead

Shifted to required: true. All scheduled workflows provide image_type: generic currently.

holmanb · 2026-05-06T23:22:00Z

+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd  # v6.0.2
+      - name: Setup LXD
+        if: ${{ contains(fromJSON('["lxd_vm", "lxd_container"]'), env.CLOUD_INIT_PLATFORM ) }}
+        uses: canonical/setup-lxd@8c6a87bfb56aa48f3fb9b830baa18562d8bfd4ee # v0.1.2


I think it has a point.

I'm uncertain what point you think has been missed here. I have updated the commit hash and comment to align with the upstream repo tag # v1. This is already resolved. in the second commit from the top. 9cd0ff6.

holmanb · 2026-05-06T07:49:19Z

+      - name: Checkout
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd  # v6.0.2
+      - name: Setup LXD
+        if: ${{ contains(fromJSON('["lxd_vm", "lxd_container"]'), env.CLOUD_INIT_PLATFORM ) }}


This workflow is shared and generic. Why is an lxd specialization used here?

@holmanb the lxd specialization is here because we only want to install the lxd snaps if we are launching LXD backends for integration testing, Azure,GCE and Ec2 don't need this step. I've added a comment.

I understand why it is needed. But I still don't understand why it is needed here.

It is in 100-dispatch-common because we allow manual "Run workflow" dispatch directly from this workflow providing a dropdown choice to select the platform which can be lxd_vm or lxd_container. As a result, this conditional logic needs to be in here to allow that flexibility for a manual run which can include lxd_*

holmanb · 2026-05-06T09:38:42Z

+          # Dump secrets using a subprocess to avoid accidental leaks while debugging.
+          sh -c 'printf "%s\n" "$SSH_PUBLIC_KEY" > ~/.ssh/cloudinit_id_rsa.pub'
+          sh -c 'printf "%s\n" "$SSH_PRIVATE_KEY" > ~/.ssh/cloudinit_id_rsa'
+          chmod 600 ~/.ssh/cloudinit_id_rsa


nit: where code fails on err, this is probably fine

but as a pattern it is undesirable to chmod after writing your secret, because there is a window of time between the two commands where the secret can be accessed by code with lower permissions

Good thought. Fixed with an early touch ~/.ssh/cloudinit_id_rsa && chmod 600 ~/.ssh/cloudinit_id_rsa

blackboxsw · 2026-05-06T16:17:58Z

Success run lxd_container
success run lxd_vm
expected failure when repo PYCLOUDLIB_TOML is not base64-encoded content.
Expected Alternate distros failure fixed in separate PR

blackboxsw · 2026-05-06T16:21:49Z

@holmanb all your comments and copilot's are addressed. I've commented iwth success runs for lxd_vm and lxc_container.

blackboxsw · 2026-05-06T16:26:47Z

#6864 just landed so Alternate distros CI would pass if we rebased.

Address review comments from copilot and Brett: - update setup-lxd pinning - validate presence of non-empty required SSH_*_KEY secrets - simplifiy -z secret test conditionals to avoid multi-line issues - use install -m 600 before creating SSH_PRIVATE_KEY file - test and exit 1 on non-encoded PYCLOUDLIB_TOML repo secret - set image_type: generic as defaults in 100-dispatch-common and ec2 job.

blackboxsw · 2026-05-06T18:56:06Z

Renamed PYCLOUDLIB_TOML -> PYCLOUDLIB_TOML_B64 to indicate intent for value.
Success run lxd_vm

holmanb

Thanks for the updates.

There are still some inconsistencies and issues to figure out - and I think that some of these would have been caught by an attentive self-review. See my comments.

holmanb · 2026-05-06T22:12:00Z

+          # Dump secrets using a subprocess to avoid accidental leaks while debugging.
+          sh -c 'printf "%s\n" "$SSH_PUBLIC_KEY" > ~/.ssh/cloudinit_id_rsa.pub'
+          # Create empty cloudinit_id_rsa with file mode 600.
+          touch ~/.ssh/cloudinit_id_rsa && chmod 600 ~/.ssh/cloudinit_id_rsa


I think this would be cleaner: install -m 600 <(echo $var) file

I had used that before, but install command isn't available in the workflow and resulted in an error.

Well crud, it was a typo 'intall command not found`. Shifting it back.

holmanb · 2026-05-06T22:19:47Z

+          PYCLOUDLIB_CONFIG: ${{ runner.temp }}/pycloudlib.toml
+          CLOUD_INIT_LOCAL_LOG_PATH: ${{ github.workspace }}/cloud_init_test_logs
+        run: |
+          tox -e integration-tests -- --ctrf=${{ github.workspace }}/report.json --color=yes ${{ inputs.filter_tests || 'tests/integration_tests' }}


Why is a default value conditionally set in test logic?

You are right, it is unnecessary, when absent we won't provide any test paths and cloud-init integration tests will default to tests/integration_tests

Actually, in testing, the absence of that default/fallback results in dependency errors from unittests this happens because we are already providing posargs which causes tox to drop the default of tests/integration_tests from tox.ini and try to run all tests in all directories. So, unittest dependencies end up 'missing' from integration-test target in this case.

So, we still need a default of fiilter_tests is unset or empty. Given that our workflow dispatch doesn't have a default, the value of filter_tests is an empty string if unspecified. We need the fallback conditional on an empty value to ensure we pass a reasonable posarg to pyttest for the integration-test target. So this logic needs to remain.

holmanb · 2026-05-06T22:30:30Z

+        run: |
+          sh -c 'echo "${{ secrets.PYCLOUDLIB_TOML_B64}}" | base64 -d > "$PYCLOUDLIB_CONFIG"' | true
+          if [ ! -s $PYCLOUDLIB_CONFIG ]; then
+            echo "PYCLOUDLIB_TOML_B64 repo secret is not a base64-encoded string"


I would just let it exit on error rather than suppressing the error and trying to add a message.

This message assumes a particular failure mode, when in fact multiple failure modes are possible.

Sure, dropped, it will fail in either case. without a specific message you will still see a `base64 error invalid input"

holmanb · 2026-05-06T22:35:24Z

+      - name: Assert required repo secrets are set
+        run: |
+          if [ -z "$REQUIRED_SECRET" ]; then
+             echo "ERROR: Missing required repo secrets.PYCLOUDLIB_TOML_B64 non-empty value."


The error message has some issues.

The non-empty value part is confusing. Also, putting a variable name in an error message means this could unknowingly become stale.

Rather than trying to diagnose the root cause of an issue in an error message, why not just state the problem in a clear way?

I have adapted the message to:
ERROR: Missing required repo secret. Please provide the necessary repo secret at ${{ github.repository }}/settings/secrets/action.

holmanb · 2026-05-06T22:37:24Z

+        type: string
+        default: 'ppa:cloud-init-dev/daily'
+  schedule:
+    # Run Mon & Thurs for high-cost test runs


are the costs really high?

higher than lxd* on the local worker. We can measure this once we turn on the new workflows.

holmanb · 2026-05-06T22:44:05Z

+    with:
+      release: jammy
+      platform: ec2
+      install_source: ${{ inputs.install_source || 'ppa:cloud-init-dev/daily' }}


Isn't this value conditionally set elsewhere?

No, this is only conditionally set if we manually use workflow-dispatch via Run workflow button on the specific job. It is not set automatically for the scheduled workflow runner so we need a default in that case.

holmanb · 2026-05-06T22:49:26Z

 pycloudlib>=1!10.0.2,<1!11

 pytest-timeout
+pytest-json-ctrf  # Used for GH ctrf.io test report dashboard


It looks like this project is no longer supported?

Meh, this README update happened after opening this original PR, having seen recent releases this year prior to that event. Strange, pypi also has an updated release one month ago, despite this project mentioning unsupported nature now. I guess we can go back to the supported junit-to-ctrf integrations-config that is currently in tip of main.

junit-to-ctrf is part of the ctrf projecthttps://github.com/ctrf-io/junit-to-ctrf. And it's under active maintenance with active security advisory handling

holmanb · 2026-05-06T23:09:30Z

+        - lxd_container
+        - lxd_vm
+        - ec2
+      image_type:


Is this needed?

yes each parameter is needed to manually dispatch the workflow as seen when clicking the run workflow button on the workflow dispatch page. Without these values being selectable, we can't manually dispatch the workflow as those required inputs would be missing.

Yes, I see that you made it required. What is it needed for?

holmanb · 2026-05-06T23:23:33Z

Also, I just unresolved some copilot reviews with comments.

blackboxsw

Thank you again @holmanb for finding the gaps or inconsistencies. I responded to everything I've seen open. I 'm not sure what else we need to do with setup-lxd though.

blackboxsw · 2026-05-07T01:01:02Z

+        - lxd_container
+        - lxd_vm
+        - ec2
+      image_type:


yes each parameter is needed to manually dispatch the workflow as seen when clicking the run workflow button on the workflow dispatch page. Without these values being selectable, we can't manually dispatch the workflow as those required inputs would be missing.

blackboxsw · 2026-05-07T01:01:43Z

+        options:
+        - generic
+        - minimal
+        required: false


Shifted to required: true. All scheduled workflows provide image_type: generic currently.

blackboxsw · 2026-05-07T01:09:39Z

+      - name: Assert required repo secrets are set
+        run: |
+          if [ -z "$REQUIRED_SECRET" ]; then
+             echo "ERROR: Missing required repo secrets.PYCLOUDLIB_TOML_B64 non-empty value."


I have adapted the message to:
ERROR: Missing required repo secret. Please provide the necessary repo secret at ${{ github.repository }}/settings/secrets/action.

blackboxsw · 2026-05-07T01:11:26Z

+        run: |
+          sh -c 'echo "${{ secrets.PYCLOUDLIB_TOML}}" | base64 -d > "$PYCLOUDLIB_CONFIG"'


After review, we'll allow the base64 -d failure and non-zero exit code leave us with an adequate breadcrumb to resolve this.

blackboxsw · 2026-05-07T01:12:16Z

+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd  # v6.0.2
+      - name: Setup LXD
+        if: ${{ contains(fromJSON('["lxd_vm", "lxd_container"]'), env.CLOUD_INIT_PLATFORM ) }}
+        uses: canonical/setup-lxd@8c6a87bfb56aa48f3fb9b830baa18562d8bfd4ee # v0.1.2


I'm uncertain what point you think has been missed here. I have updated the commit hash and comment to align with the upstream repo tag # v1. This is already resolved. in the second commit from the top. 9cd0ff6.

blackboxsw · 2026-05-07T03:17:23Z

+    with:
+      release: jammy
+      platform: ec2
+      install_source: ${{ inputs.install_source || 'ppa:cloud-init-dev/daily' }}


No, this is only conditionally set if we manually use workflow-dispatch via Run workflow button on the specific job. It is not set automatically for the scheduled workflow runner so we need a default in that case.

blackboxsw · 2026-05-07T03:36:04Z

+    uses: ./.github/workflows/100-dispatch-common.yml
+    with:
+      release: resolute
+      platform: ec2


Given that we now decided below to shift this to a required parameter, all workflows will provide image_type for both cheduled and manual workflow dispatch.

blackboxsw · 2026-05-07T04:01:57Z

+      - name: Checkout
+        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd  # v6.0.2
+      - name: Setup LXD
+        if: ${{ contains(fromJSON('["lxd_vm", "lxd_container"]'), env.CLOUD_INIT_PLATFORM ) }}


It is in 100-dispatch-common because we allow manual "Run workflow" dispatch directly from this workflow providing a dropdown choice to select the platform which can be lxd_vm or lxd_container. As a result, this conditional logic needs to be in here to allow that flexibility for a manual run which can include lxd_*

blackboxsw · 2026-05-07T04:09:36Z

+          # Dump secrets using a subprocess to avoid accidental leaks while debugging.
+          sh -c 'printf "%s\n" "$SSH_PUBLIC_KEY" > ~/.ssh/cloudinit_id_rsa.pub'
+          # Create empty cloudinit_id_rsa with file mode 600.
+          touch ~/.ssh/cloudinit_id_rsa && chmod 600 ~/.ssh/cloudinit_id_rsa


Well crud, it was a typo 'intall command not found`. Shifting it back.

Migrate away from deprecated pytest-json-ctrf reverting to use ctrf intrgration junit-to-ctrf.

blackboxsw force-pushed the ci-lxd-vm branch 2 times, most recently from 4f73b0f to ed8690d Compare February 5, 2026 05:20

blackboxsw marked this pull request as draft February 5, 2026 05:21

blackboxsw force-pushed the ci-lxd-vm branch from ed8690d to 69bffdf Compare February 5, 2026 14:18

holmanb reviewed Feb 5, 2026

View reviewed changes

holmanb self-assigned this Feb 5, 2026

holmanb added the incomplete Action required by submitter label Feb 10, 2026

blackboxsw force-pushed the ci-lxd-vm branch from b16406d to be806da Compare February 11, 2026 23:20

blackboxsw commented Feb 11, 2026

View reviewed changes

blackboxsw requested a review from holmanb February 11, 2026 23:27

blackboxsw removed the incomplete Action required by submitter label Feb 11, 2026

blackboxsw marked this pull request as ready for review February 13, 2026 04:32

holmanb reviewed Feb 19, 2026

View reviewed changes

holmanb added the incomplete Action required by submitter label Feb 26, 2026

blackboxsw force-pushed the ci-lxd-vm branch 7 times, most recently from 0c75a04 to 3937aae Compare March 10, 2026 21:15

github-actions Bot added the stale-pr Pull request is stale; will be auto-closed soon label Mar 31, 2026

canonical deleted a comment from github-actions Bot Apr 6, 2026

blackboxsw force-pushed the ci-lxd-vm branch from cf7193d to 0d71747 Compare April 6, 2026 21:47

holmanb reviewed Apr 6, 2026

View reviewed changes

github-actions Bot removed the stale-pr Pull request is stale; will be auto-closed soon label Apr 7, 2026

blackboxsw requested a review from holmanb April 7, 2026 14:11

blackboxsw removed the incomplete Action required by submitter label Apr 7, 2026

blackboxsw added 4 commits April 17, 2026 03:34

blackboxsw force-pushed the ci-lxd-vm branch from 8d06317 to 24c62a7 Compare April 20, 2026 14:30

blackboxsw requested a review from holmanb April 24, 2026 21:01

holmanb requested a review from Copilot May 6, 2026 07:43

Copilot started reviewing on behalf of holmanb May 6, 2026 07:44 View session

Copilot AI reviewed May 6, 2026

View reviewed changes

holmanb requested changes May 6, 2026

View reviewed changes

blackboxsw force-pushed the ci-lxd-vm branch from 33030e6 to 9f06afc Compare May 6, 2026 16:01

blackboxsw requested a review from holmanb May 6, 2026 16:18

blackboxsw force-pushed the ci-lxd-vm branch from 9f06afc to 84aaeac Compare May 6, 2026 16:44

holmanb requested changes May 6, 2026

View reviewed changes

blackboxsw force-pushed the ci-lxd-vm branch from 84aaeac to 68fad41 Compare May 7, 2026 03:48

ci: rename PYCLOUDLIB_TOML_B64 to indicate base64-encoded

cbfe7c6

blackboxsw force-pushed the ci-lxd-vm branch 2 times, most recently from ef54ca4 to fbbc886 Compare May 7, 2026 04:11

blackboxsw commented May 7, 2026

View reviewed changes

blackboxsw requested a review from holmanb May 7, 2026 04:13

blackboxsw force-pushed the ci-lxd-vm branch from fbbc886 to 2eed7fb Compare May 16, 2026 23:18

ci: standardize input/dispatch defaults, errors for missing secrets

30090a6

Migrate away from deprecated pytest-json-ctrf reverting to use ctrf intrgration junit-to-ctrf.

blackboxsw force-pushed the ci-lxd-vm branch from 2eed7fb to 30090a6 Compare May 17, 2026 00:31

		test '${{ secrets.PYCLOUDLIB_TOML }}' != '' \|\| echo "ERROR: Missing required repo secrets.PYCLOUDLIB_TOML non-empty value."
		test '${{ secrets.PYCLOUDLIB_TOML }}' == '' && exit 1

		run: \|
		sh -c 'echo "${{ secrets.PYCLOUDLIB_TOML}}" \| base64 -d > "$PYCLOUDLIB_CONFIG"'

Conversation

blackboxsw commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Proposed Commit Message

Additional Context

Test Steps

Merge type

Uh oh!

holmanb left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

blackboxsw Feb 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

holmanb commented Mar 16, 2026

Uh oh!

holmanb left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

blackboxsw Apr 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

blackboxsw commented Apr 7, 2026

Uh oh!

blackboxsw commented Apr 24, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

blackboxsw commented Feb 5, 2026 •

edited

Loading

blackboxsw Feb 11, 2026 •

edited

Loading

blackboxsw Apr 7, 2026 •

edited

Loading

blackboxsw May 6, 2026 •

edited

Loading

blackboxsw commented May 6, 2026 •

edited

Loading

holmanb left a comment •

edited

Loading