Deployment dependency between parameters #16667
Unanswered
guimatheus92
asked this question in
Ideas
Replies: 1 comment
|
Adding you here @GABRIELNGBTUC since you helped me a lot already 👌 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
We have the
dependsOnfeature, where we can set resource dependencies within Bicep templates.I have worked in some projects where we used to define each resource separately in different files instead of modules, and for each resource, there could be one or more
.bicepparamfiles for a given template.So the problem is when we try to deploy using the
az deployment group create, I would like to create a chain of dependencies between them and deploy them all at once and a dependency would be respected.I don't know if there is a way to achieve that, but if not, I would suggest to create any feature in Bicep where we can define all parameters files we want to deploy and maybe set a dependency with
dependsOnalso, that way I can manage files separately and deploy them together.Project structure is like this:
How could I deploy
MachineLearningWorkspace.mlwmlwalias1int01.Parameter.bicepparamonly afterStorageAccount.stmonitoringint01.Parameter.bicepparamfor example?All reactions