Skip to content

test(recipes): re-enable custom terraform recipe functional test #13312

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nicolejms merged 2 commits into from
Oct 15, 2026
Merged

test(recipes): re-enable custom terraform recipe functional test #13312

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
962098b
test(recipes): re-enable custom terraform recipe functional test
nicolejms Oct 15, 2026
651ad58
docs(testing): remove obsolete skipped custom-case note
nicolejms Oct 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions ...tributing/contributing-code/contributing-code-tests/running-functional-tests.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -263,8 +263,6 @@ The GitHub Actions role allows 5400-second sessions, and the LRT workflow reques

`Test_TerraformRecipe_AzureResourceGroup` in `test/functional-portable/corerp/cloud/resources` checks both the registered Azure provider and a custom provider alias. The custom case loads the tenant from a secret store, loads the client ID through `envSecrets`, and enables OIDC through `env`. Invalid environment defaults ensure the explicit provider fields and secret-backed environment value must take effect. It uses the registered Azure workload identity and replaces the skipped PostgreSQL provider test; no database or fixed readiness delay is needed. The custom case uses a separate fixture, `corerp-resources-terraform-azurerg-custom-provider.bicep`, so neither fixture needs conditional resources.

The custom case is skipped until [#13299](https://github.com/radius-project/radius/issues/13299) is fixed. Radius runs `terraform get` before it adds aliased providers, so modules that declare `configuration_aliases` fail to download. Remove the skip as part of that fix.

Both cases keep their Kubernetes state Secret until normal Terraform destroy completes. The Terraform driver does not record Azure scope IDs, such as resource groups, as output resources, so the test uses the Azure SDK instead. It checks that the Azure resource group exists after deployment and that both the group and state Secret are absent after deletion, even when `RADIUS_TEST_FAST_CLEANUP=true`. SDK fallback cleanup runs only after those checks and cannot turn a failed destroy into a passing test.

Use the normal cloud-suite setup, including `AZURE_SUBSCRIPTION_ID`, the Terraform module server, and the same Entra service principal for the runner and Radius pods. The custom case reads `AZURE_SP_TESTS_TENANTID` and `AZURE_SP_TESTS_APPID`, or the service-principal identity from `az account show`. Publish both `azure-rg` and `azure-rg-custom-provider` with `make publish-test-terraform-recipes`, then run:
Expand Down
3 changes: 0 additions & 3 deletions test/functional-portable/corerp/cloud/resources/recipe_terraform_test.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,9 +55,6 @@ func Test_TerraformRecipe_AzureResourceGroup(t *testing.T) {
label = "custom"
}
t.Run(label, func(t *testing.T) {
if custom {
t.Skip("Terraform get rejects modules with provider configuration_aliases: https://github.com/radius-project/radius/issues/13299")
}
ctx := t.Context()
Comment thread
nicolejms marked this conversation as resolved.
name := "corerp-resources-terraform-azrg-" + label
appName, envName := name+"-app", name+"-env"
Expand Down
Loading