Skip to content

fix: surface azure custom stack outputs via phone home#1943

Merged
im-Amitto merged 2 commits into
mainfrom
am/azure-custom-stack-outputs
Jul 19, 2026
Merged

fix: surface azure custom stack outputs via phone home#1943
im-Amitto merged 2 commits into
mainfrom
am/azure-custom-stack-outputs

Conversation

@im-Amitto

Copy link
Copy Markdown
Contributor

azure-bicep already deploys custom_nested_stacks (arm/linked_deployment_custom.go), but their outputs never reach the phone-home payload — so {{ .nuon.install_stack.outputs.custom_nested_stacks.* }} resolves on aws and silently never populates on azure.

  • collect each custom deployment's template output keys during composition
  • add them to the phone-home script as env vars ([string(reference('<deployment>').outputs.<key>.value)]) and a custom_nested_stacks payload field mirroring the aws lambda shape, with dependsOn on each custom deployment
  • reorder template composition so the phone-home resource is built after custom deployments
  • reject custom_nested_stacks on gcp-terraform at config parse — the gcp renderer ignores them, so today they validate, upload, and then silently do nothing

Non-string ARM outputs are serialized with string().

@im-Amitto
im-Amitto force-pushed the am/azure-custom-stack-outputs branch from e328841 to 851b7f7 Compare July 19, 2026 21:50
@im-Amitto
im-Amitto merged commit 58983d4 into main Jul 19, 2026
27 checks passed
@im-Amitto
im-Amitto deleted the am/azure-custom-stack-outputs branch July 19, 2026 22:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants