Uh oh!
There was an error while loading. Please reload this page.
Repo structure after pull - to be followed with Bicep deployments? #643
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi there project maintainers and contributors. Repo structure after pull is great. But when working with Bicep or JSON for new/or change in existing configuration deployments, should deployments just be under the same structure? Should i just create I have tested that and it works well. It is also pulling the created resource/s with their .json after with the unique identifier. But that is duplication, so I am doubting using Is this how it is supposed to be managed? I don't fully understand the documentation: Do the project have some examples around this certain topic? It seems to be very intelligent. First time it deploys the Truly grateful for answers. /b |
Replies: 2 comments 8 replies
Can be closed. After watching the great video from Simon Wåhlin I got all the answers. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Simon Wåhlin (@SimonWahlin) I'm struggling with the way of working even after watching the video. You dump e.g. a storage.bicep file in a folder. After a full cycle it becomes obsolete imo, since the pull generates this unique arm template for that same storage.bicep. To keep the repo clean, should I remove the storage.bicep? |



Can be closed.
After watching the great video from Simon Wåhlin I got all the answers.