Forum Discussion
Solved
Copying template.json from Export Template and deploy in bicep
I have a question, i want to deploy my resources (already created on Azure Portal) on my Azure Dev Ops Repo. My question is: is it legit to take the template.json from Export Template and then conver...
- I am also generally in favour of building things up from the base. The template.json file can help you with this and simplify the start.
thank you very much, yeah i thought my question was not good enough and often people then ignore!
But what things should be modified? Is it not better than to start from scratch especially for things like azure functions? It would be not so much time-consuming?
But what things should be modified? Is it not better than to start from scratch especially for things like azure functions? It would be not so much time-consuming?
Even though it's late, I hope this comment is still useful for you or anyone else who comes across this post.
The ARM to Bicep conversion process is quite effective, but it isn’t flawless. Some complex constructs or specific resource configurations in ARM JSON may not convert smoothly into Bicep. You might encounter:
Syntax errors or warnings that require addressing after conversion.
Certain features, such as complex nested deployments, may not decompile correctly and might need manual intervention to fix.
Exported ARM templates may also contain hidden dependencies that aren’t immediately obvious, and these can be carried over directly into the Bicep code. This makes it more challenging to refactor and reorganize the template effectively, particularly when extracting reusable modules.
Hope this helps.
The ARM to Bicep conversion process is quite effective, but it isn’t flawless. Some complex constructs or specific resource configurations in ARM JSON may not convert smoothly into Bicep. You might encounter:
Syntax errors or warnings that require addressing after conversion.
Certain features, such as complex nested deployments, may not decompile correctly and might need manual intervention to fix.
Exported ARM templates may also contain hidden dependencies that aren’t immediately obvious, and these can be carried over directly into the Bicep code. This makes it more challenging to refactor and reorganize the template effectively, particularly when extracting reusable modules.
Hope this helps.