Support step output variables in ARM templates
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 19
- Avg merge
- 11m
- Merged PRs (30d)
- 2
Description
This is a take-away item from #3. A nice feature for the ARM runner would be to support a similar concept of propagated step variables like in the Terraform runner.
We can probably implement this by leveraging the template output feature via Azure CLI. The current implementation in #3 creates individual deployment metadata for each step, so we can most likely implement some logic to parse the outputs from previous steps and expose them as variables to later step ARM templates.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #3 and the current ARM runner behavior that creates deployment metadata for each step. Trace how Azure CLI template outputs could be parsed and exposed to later ARM templates; done means a later step can consume output variables from an earlier step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go, terraform
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100