You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: