Skip to content

Migrate to new Azure tenant#11269

Merged
willdavsmith merged 30 commits intoradius-project:mainfrom
willdavsmith:0217ftfixes
Feb 23, 2026
Merged

Migrate to new Azure tenant#11269
willdavsmith merged 30 commits intoradius-project:mainfrom
willdavsmith:0217ftfixes

Conversation

@willdavsmith
Copy link
Contributor

@willdavsmith willdavsmith commented Feb 19, 2026

NOTE: the cloud tests are failing in this PR. it seems to be running the version of the workflow from main. this should be resolved when it's merged into main.

Description

  • Migrate to new Azure tenant
  • Use resources deployed via Terraform
  • Improve fork-ability of repo

[Fork] Passing LRT run: https://github.com/willdavsmith/radius/actions/runs/22155234512
Passing Cloud test run: https://github.com/willdavsmith/radius/actions/runs/22124974117

[main] Passing Cloud test run: https://github.com/radius-project/radius/actions/runs/22317562274
[main] Passing long-running test run: https://github.com/radius-project/radius/actions/runs/22248761002

New/updated GitHub variables:

AZURE_LOCATION
AWS_REGION
BICEP_TYPES_REGISTRY
FUNCTIONAL_TEST_APP_ID
FUNCTIONAL_TEST_BICEP_RECIPE_REGISTRY
FUNCTIONAL_TEST_CONTAINER_REGISTRY
LRT_AKS_CLUSTER_NAME
LRT_AKS_RESOURCE_GROUP
RADIUS_REPOSITORY
TEST_BICEP_TYPES_REGISTRY

New/updated GitHub secrets:

AZURE_SP_TESTS_APPID
AZURE_SP_TESTS_TENANTID
AZURE_SUBSCRIPTIONID_TESTS
BICEPTYPES_CLIENT_ID
BICEPTYPES_SUBSCRIPTION_ID
BICEPTYPES_TENANT_ID
FUNCTEST_AZURE_OIDC_JSON
FUNCTEST_PREPROVISIONED_RESOURCE_JSON
FUNCTIONAL_TEST_APP_PRIVATE_KEY

Type of change

  • This pull request adds or changes features of Radius and has an approved issue (issue link required).

Fixes: #issue_number

Contributor checklist

Please verify that the PR meets the following requirements, where applicable:

  • An overview of proposed schema changes is included in a linked GitHub issue.
    • Yes
    • Not applicable
  • A design document PR is created in the design-notes repository, if new APIs are being introduced.
    • Yes
    • Not applicable
  • The design document has been reviewed and approved by Radius maintainers/approvers.
    • Yes
    • Not applicable
  • A PR for the samples repository is created, if existing samples are affected by the changes in this PR.
    • Yes
    • Not applicable
  • A PR for the documentation repository is created, if the changes in this PR affect the documentation or any user facing updates are made.
    • Yes
    • Not applicable
  • A PR for the recipes repository is created, if existing recipes are affected by the changes in this PR.
    • Yes
    • Not applicable

Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Signed-off-by: willdavsmith <willdavsmith@gmail.com>
Signed-off-by: willdavsmith <willdavsmith@gmail.com>
@willdavsmith willdavsmith requested a deployment to external-contributor-approval February 19, 2026 17:12 — with GitHub Actions Waiting
if ! rad install kubernetes \
--set global.azureWorkloadIdentity.enabled=true \
--set database.enabled=true; then
--set database.enabled=false; then
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new tenants have pretty tight quotas, and the database feature doesn't seem to work in single-node AKS. disabling for now.

Signed-off-by: willdavsmith <willdavsmith@gmail.com>
@willdavsmith willdavsmith temporarily deployed to external-contributor-approval February 19, 2026 21:30 — with GitHub Actions Inactive
@codecov
Copy link

codecov bot commented Feb 19, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 50.98%. Comparing base (209adb7) to head (b6553f5).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #11269   +/-   ##
=======================================
  Coverage   50.98%   50.98%           
=======================================
  Files         679      679           
  Lines       43174    43174           
=======================================
+ Hits        22012    22013    +1     
+ Misses      19040    19038    -2     
- Partials     2122     2123    +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@willdavsmith willdavsmith temporarily deployed to external-contributor-approval February 19, 2026 23:05 — with GitHub Actions Inactive
Signed-off-by: willdavsmith <willdavsmith@gmail.com>
@willdavsmith willdavsmith requested a deployment to external-contributor-approval February 20, 2026 22:42 — with GitHub Actions Waiting
Signed-off-by: willdavsmith <willdavsmith@gmail.com>
@willdavsmith willdavsmith requested a deployment to external-contributor-approval February 20, 2026 22:59 — with GitHub Actions Waiting
AZURE_WORKLOAD_IDENTITY_WEBHOOK_VER: 1.3.0
# Container registry for storing container images
CONTAINER_REGISTRY: ghcr.io/radius-project/dev
CONTAINER_REGISTRY: ${{ vars.FUNCTIONAL_TEST_CONTAINER_REGISTRY }}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

setting these in vars makes forkability much easier.


- name: Get App Token (radius-publisher)
uses: actions/create-github-app-token@29824e69f54612133e76f7eaac726eef6c875baf # v2.2.1
id: get_publisher_token
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we need the publishing steps for the functional test workflows. I refactored to use BICEP_TYPES_REGISTRY (public) for pulling types, and TEST_BICEP_TYPES_REGISTRY any time we need to push types.

},
"cloud": {
"credentialPrecedence": ["Environment"]
"credentialPrecedence": ["AzureCLI", "Environment"]
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for private ACR

)

func Test_AWSRedeployWithUpdatedResourceUpdatesResource(t *testing.T) {
t.Skip("temporarily skipping AWS tests while OIDC issuer validation is being updated")
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I need to talk to Nithya today about the setup. the rest of the PR can be reviewed but I'll leave it in draft state until this part is ready.

@willdavsmith willdavsmith changed the title [WIP/ Do not review] Migrate to new Azure tenant Migrate to new Azure tenant Feb 23, 2026
FUNCTIONALTEST_TIMEOUT: 60m
# The Azure Location to store test resources
AZURE_LOCATION: westus3
AZURE_LOCATION: westus2
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: move to vars as well

steps:
- name: Get GitHub app token
if: github.repository == 'radius-project/radius'
if: github.repository == vars.RADIUS_REPOSITORY
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: keeping hard-codded is fine in this case

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to test on a fork, I had to set up a GitHub app, so I think this one should still be a var

Signed-off-by: willdavsmith <willdavsmith@gmail.com>
@willdavsmith willdavsmith temporarily deployed to external-contributor-approval February 23, 2026 17:32 — with GitHub Actions Inactive
@willdavsmith willdavsmith marked this pull request as ready for review February 23, 2026 18:07
@willdavsmith willdavsmith requested review from a team as code owners February 23, 2026 18:07
Copilot AI review requested due to automatic review settings February 23, 2026 18:07
@radius-functional-tests
Copy link

radius-functional-tests bot commented Feb 23, 2026

Radius functional test overview

🔍 Go to test action run

Click here to see the test run details
Name Value
Repository willdavsmith/radius
Commit ref 4a191cd
Unique ID func1d0d378bfc
Image tag pr-func1d0d378bfc
  • gotestsum 1.13.0
  • KinD: v0.29.0
  • Dapr: 1.14.4
  • Azure KeyVault CSI driver: 1.4.2
  • Azure Workload identity webhook: 1.3.0
  • Bicep recipe location ghcr.io/radius-project/dev/test/testrecipes/test-bicep-recipes/<name>:pr-func1d0d378bfc
  • Terraform recipe location http://tf-module-server.radius-test-tf-module-server.svc.cluster.local/<name>.zip (in cluster)
  • applications-rp test image location: ghcr.io/radius-project/dev/applications-rp:pr-func1d0d378bfc
  • dynamic-rp test image location: ghcr.io/radius-project/dev/dynamic-rp:pr-func1d0d378bfc
  • controller test image location: ghcr.io/radius-project/dev/controller:pr-func1d0d378bfc
  • ucp test image location: ghcr.io/radius-project/dev/ucpd:pr-func1d0d378bfc
  • deployment-engine test image location: ghcr.io/radius-project/deployment-engine:latest

Test Status

⌛ Building Radius and pushing container images for functional tests...
✅ Container images build succeeded
⌛ Publishing Bicep Recipes for functional tests...
✅ Recipe publishing succeeded
⌛ Starting corerp-cloud functional tests...
⌛ Starting ucp-cloud functional tests...
❌ Test tool installation for corerp-cloud failed. Please check the logs for more details
❌ Test tool installation for ucp-cloud failed. Please check the logs for more details
❌ Failed to install Radius for ucp-cloud functional test. Please check the logs for more details
❌ corerp-cloud functional test failed. Please check the logs for more details
❌ ucp-cloud functional test failed. Please check the logs for more details

# AZURE_OIDC_ISSUER_PUBLIC_KEY
# AZURE_OIDC_ISSUER_PRIVATE_KEY
# AZURE_OIDC_ISSUER
eval "export $(echo "${{ secrets.FUNCTEST_AZURE_OIDC_JSON }}" | jq -r 'to_entries | map("\(.key)=\(.value)") | @sh')"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure how they were set before, but I kept getting parsing issues for these secrets when exported from Terraform. these should fix it

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request migrates the Radius project to a new Azure tenant, replaces hardcoded values with GitHub variables for better fork-ability, and modernizes the Bicep types publishing approach. The changes eliminate the complex remote workflow dispatch pattern by implementing direct publishing of Bicep types, improving testability and reducing dependencies. The PR also enhances security by adding proper JSON validation, improving credential handling, and migrating from PAT tokens to the built-in github.token where possible.

Changes:

  • Replaced hardcoded Azure configuration values with GitHub variables (location, cluster names, registry URLs, app IDs)
  • Simplified Bicep types publishing by removing remote repository dispatch in favor of direct publishing to ACR
  • Improved JSON parsing for secrets with proper validation using jq -e and error handling
  • Enhanced fork-ability by using vars.RADIUS_REPOSITORY and migrating from PAT to github.token in most workflows
  • Disabled database for Radius installation in manage-radius-installation.sh
  • Added proper conditional checks and permissions for workflow jobs

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File Description
.github/workflows/long-running-azure.yaml Updated environment variables to use GitHub vars, improved JSON parsing, added bicepconfig.json update step, changed database.enabled to false, missing permissions block in report-failure job
.github/workflows/functional-test-noncloud.yaml Updated repository checks to use vars.RADIUS_REPOSITORY, migrated to github.token, added issues:write permission
.github/workflows/functional-test-cloud.yaml Removed complex remote workflow dispatch for Bicep types publishing, implemented direct publishing approach, improved OIDC key validation with openssl, enhanced JSON parsing with validation, added packages:read permission, added conditional checks with always()
.github/scripts/manage-radius-installation.sh Changed database.enabled from true to false for Radius installation

@brooke-hamilton brooke-hamilton self-requested a review February 23, 2026 19:14
Copy link
Member

@brooke-hamilton brooke-hamilton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

Minor issues only below.

Comment on lines 274 to 279
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Duplicate Checkout step

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oops

permissions: {}
if: failure() && github.event_name == 'schedule' && github.repository == 'radius-project/radius'
if: failure() && github.event_name == 'schedule' && github.repository == vars.RADIUS_REPOSITORY
steps:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this job need write permissions for issues?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no, because it's using GH_RAD_CI_BOT_PAT. we would only need permissions if we were using the default GITHUB_TOKEN (github.token)

- name: Create failure issue for failing scheduled run
uses: actions/github-script@ed597411d8f924073f98dfc5c65a23a2325f34cd # v8.0.0
with:
github-token: ${{ secrets.GH_RAD_CI_BOT_PAT }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just verifying - does this workflow still use the PAT, or was the PAT removed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this workflow still uses the PAT. it's only using it here though (for issue creation) because I didn't want to affect that flow in this PR. it was removed everywhere else in the PR because it was possible to use the default github.token for the purpose.

Signed-off-by: willdavsmith <willdavsmith@gmail.com>
@willdavsmith willdavsmith requested a deployment to external-contributor-approval February 23, 2026 22:40 — with GitHub Actions Waiting
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 12 comments.

steps:
- name: Get GitHub app token
if: github.repository == 'radius-project/radius'
if: github.repository == vars.RADIUS_REPOSITORY
Copy link

Copilot AI Feb 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The vars.RADIUS_REPOSITORY variable is used in conditional expressions without the ${{ }} wrapper. In GitHub Actions, when accessing vars context in if conditions, you must use the ${{ }} wrapper. The correct syntax is:

if: github.repository == '${{ vars.RADIUS_REPOSITORY }}'

Without the wrapper and quotes, the expression will be evaluated as a literal string comparison against "vars.RADIUS_REPOSITORY" rather than the actual variable value. This affects multiple step-level conditionals in this file.

Suggested change
if: github.repository == vars.RADIUS_REPOSITORY
if: github.repository == '${{ vars.RADIUS_REPOSITORY }}'

Copilot uses AI. Check for mistakes.
uses: ./.github/actions/process-test-results
# In case of failure, upload functional_test_results to artifacts so that they are not erased by subsequent runs.
if: failure() && github.repository == 'radius-project/radius'
if: failure() && github.repository == vars.RADIUS_REPOSITORY
Copy link

Copilot AI Feb 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The vars.RADIUS_REPOSITORY variable is used in conditional expressions without the ${{ }} wrapper. In GitHub Actions, when accessing vars context in if conditions, you must use the ${{ }} wrapper. The correct syntax is:

if: failure() && github.repository == '${{ vars.RADIUS_REPOSITORY }}'

Without the wrapper and quotes, the expression will be evaluated as a literal string comparison against "vars.RADIUS_REPOSITORY" rather than the actual variable value.

Suggested change
if: failure() && github.repository == vars.RADIUS_REPOSITORY
if: failure() && github.repository == '${{ vars.RADIUS_REPOSITORY }}'

Copilot uses AI. Check for mistakes.
report-test-results:
# Report final test status. Runs after all tests complete (or are skipped).
if: always() && github.repository == 'radius-project/radius'
if: always() && github.repository == vars.RADIUS_REPOSITORY
Copy link

Copilot AI Feb 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The vars.RADIUS_REPOSITORY variable is used in conditional expressions without the ${{ }} wrapper. In GitHub Actions, when accessing vars context in if conditions, you must use the ${{ }} wrapper. The correct syntax is:

if: always() && github.repository == '${{ vars.RADIUS_REPOSITORY }}'

Without the wrapper and quotes, the expression will be evaluated as a literal string comparison against "vars.RADIUS_REPOSITORY" rather than the actual variable value.

Copilot uses AI. Check for mistakes.
timeout-minutes: 5
permissions: {}
if: failure() && github.event_name == 'schedule' && github.repository == 'radius-project/radius'
if: failure() && github.event_name == 'schedule' && github.repository == vars.RADIUS_REPOSITORY
Copy link

Copilot AI Feb 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The vars.RADIUS_REPOSITORY variable is used in conditional expressions without the ${{ }} wrapper. In GitHub Actions, when accessing vars context in if conditions, you must use the ${{ }} wrapper. The correct syntax is:

if: failure() && github.event_name == 'schedule' && github.repository == '${{ vars.RADIUS_REPOSITORY }}'

Without the wrapper and quotes, the expression will be evaluated as a literal string comparison against "vars.RADIUS_REPOSITORY" rather than the actual variable value.

Copilot uses AI. Check for mistakes.

- name: Get GitHub app token
if: github.repository == 'radius-project/radius'
if: github.repository == vars.RADIUS_REPOSITORY
Copy link

Copilot AI Feb 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The vars.RADIUS_REPOSITORY variable is used in conditional expressions without the ${{ }} wrapper. In GitHub Actions, when accessing vars context in if conditions, you must use the ${{ }} wrapper. The correct syntax is:

if: github.repository == '${{ vars.RADIUS_REPOSITORY }}'

Without the wrapper and quotes, the expression will be evaluated as a literal string comparison against "vars.RADIUS_REPOSITORY" rather than the actual variable value.

Copilot uses AI. Check for mistakes.
steps:
- name: Get GitHub app token
if: github.repository == 'radius-project/radius'
if: github.repository == vars.RADIUS_REPOSITORY
Copy link

Copilot AI Feb 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The vars.RADIUS_REPOSITORY variable is used in conditional expressions without the ${{ }} wrapper. In GitHub Actions, when accessing vars context in if conditions, you must use the ${{ }} wrapper. The correct syntax is:

if: github.repository == '${{ vars.RADIUS_REPOSITORY }}'

Without the wrapper and quotes, the expression will be evaluated as a literal string comparison against "vars.RADIUS_REPOSITORY" rather than the actual variable value.

Suggested change
if: github.repository == vars.RADIUS_REPOSITORY
if: github.repository == '${{ vars.RADIUS_REPOSITORY }}'

Copilot uses AI. Check for mistakes.
steps:
- name: Get GitHub app token
if: github.repository == 'radius-project/radius'
if: github.repository == vars.RADIUS_REPOSITORY
Copy link

Copilot AI Feb 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The vars.RADIUS_REPOSITORY variable is used in conditional expressions without the ${{ }} wrapper. In GitHub Actions, when accessing vars context in if conditions, you must use the ${{ }} wrapper. The correct syntax is:

if: github.repository == '${{ vars.RADIUS_REPOSITORY }}'

Without the wrapper and quotes, the expression will be evaluated as a literal string comparison against "vars.RADIUS_REPOSITORY" rather than the actual variable value.

Suggested change
if: github.repository == vars.RADIUS_REPOSITORY
if: github.repository == '${{ vars.RADIUS_REPOSITORY }}'

Copilot uses AI. Check for mistakes.
jobs:
tests:
if: github.repository == 'radius-project/radius'
if: github.repository == vars.RADIUS_REPOSITORY
Copy link

Copilot AI Feb 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The vars.RADIUS_REPOSITORY variable is used in conditional expressions without the ${{ }} wrapper. In GitHub Actions, when accessing vars context in if conditions, you must use the ${{ }} wrapper. The correct syntax is:

if: github.repository == '${{ vars.RADIUS_REPOSITORY }}'

Without the wrapper and quotes, the expression will be evaluated as a literal string comparison against "vars.RADIUS_REPOSITORY" rather than the actual variable value. This affects multiple locations in this file.

Suggested change
if: github.repository == vars.RADIUS_REPOSITORY
if: github.repository == '${{ vars.RADIUS_REPOSITORY }}'

Copilot uses AI. Check for mistakes.
uses: ./.github/actions/process-test-results
# In case of failure, upload functional_test_results to artifacts so that they are not erased by subsequent runs.
if: failure() && github.repository == 'radius-project/radius'
if: failure() && github.repository == vars.RADIUS_REPOSITORY
Copy link

Copilot AI Feb 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The vars.RADIUS_REPOSITORY variable is used in conditional expressions without the ${{ }} wrapper. In GitHub Actions, when accessing vars context in if conditions, you must use the ${{ }} wrapper. The correct syntax is:

if: failure() && github.repository == '${{ vars.RADIUS_REPOSITORY }}'

Without the wrapper and quotes, the expression will be evaluated as a literal string comparison against "vars.RADIUS_REPOSITORY" rather than the actual variable value.

Suggested change
if: failure() && github.repository == vars.RADIUS_REPOSITORY
if: failure() && github.repository == '${{ vars.RADIUS_REPOSITORY }}'

Copilot uses AI. Check for mistakes.
always() &&
(github.event_name != 'pull_request_target' || needs.approval-gate.result == 'success' || needs.approval-gate.result == 'skipped') &&
(github.event_name != 'schedule' || github.repository == 'radius-project/radius')
(github.event_name != 'schedule' || github.repository == vars.RADIUS_REPOSITORY)
Copy link

Copilot AI Feb 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The vars.RADIUS_REPOSITORY variable is used in conditional expressions without the ${{ }} wrapper. In GitHub Actions, when accessing vars context in if conditions, you must use the ${{ }} wrapper. The correct syntax is:

(github.event_name != 'schedule' || github.repository == '${{ vars.RADIUS_REPOSITORY }}')

Without the wrapper and quotes, the expression will be evaluated as a literal string comparison against "vars.RADIUS_REPOSITORY" rather than the actual variable value.

Suggested change
(github.event_name != 'schedule' || github.repository == vars.RADIUS_REPOSITORY)
(github.event_name != 'schedule' || github.repository == '${{ vars.RADIUS_REPOSITORY }}')

Copilot uses AI. Check for mistakes.
@willdavsmith willdavsmith merged commit 088b1fe into radius-project:main Feb 23, 2026
45 of 46 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants