Add verification workflow for Repo Radius#12170
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
Signed-off-by: sk593 <shruthikumar@microsoft.com>
bc99ce1 to
209f96d
Compare
Radius functional test overviewClick here to see the test run details
Test Status⌛ Building Radius and pushing container images for functional tests... |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #12170 +/- ##
==========================================
- Coverage 52.33% 52.32% -0.02%
==========================================
Files 738 738
Lines 47324 47324
==========================================
- Hits 24766 24760 -6
- Misses 20192 20195 +3
- Partials 2366 2369 +3 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Description
Lands the Repo Radius verify credential-verification GitHub Actions workflow in this repository, plus a README.md documenting it.
The workflow contract is owned by Radius and consumed by the multi-cluster v1 work (#12106), so it needs a canonical, reviewed home here that any frontend (the Copilot app, the CLI, etc.) can drive.
This PR adds the verify workflow only. The companion deploy workflow and the RADIUS_TARGET_KUBECONFIG / KUBE_CONFIG_PATH integration contract will follow in a later PR.
What's added:
radius-verify-credentials.yml — a workflow_dispatch workflow that, per provider:
Authenticates to Azure/AWS via GitHub OIDC (no long-lived cloud secrets stored).
Verifies access (az account show / aws sts get-caller-identity, with the AWS account ID masked in logs).
Discovers resources (resource groups, AKS/EKS clusters, VPCs, subnets, locations) and uploads them as the radius-discovery artifact for the caller to read back.
Branches by provider so the same file serves Azure-only and AWS-only environments; steps are skipped when a provider's variables are empty.
README.md — documents the workflow's purpose, trigger, inputs, permissions, required GitHub Environment variables, and the cloud-side OIDC trust prerequisites.
Type of change
Fixes: #issue_number
Contributor checklist
Please verify that the PR meets the following requirements, where applicable:
eng/design-notes/in this repository, if new APIs are being introduced.