Thanks again for your great videos Adam. Really appreciated. My problem with Json is that I can't find Commands/Syntaxes that I can use in a template and their arguments/parameters. For example when I need to use IF function, i don't know what I can put after IF. and in what format? Also I was wondering if there is a way to see value of a variable without deploying the whole template. For example I have a StorageName variable which I need to check what its value is before the deployment. Is it possible? Thanks.
Make sure to have VS Code Azure Resource Manager tools extension installed and that $schema is up to date and that files have .json extension. Other than this press CTRL+. (dot) to show intellisense. Or check docs for reference samples.
Hi Adam, is condition property available in service bus namespace? If so which api version? Basically I have SB namespace creation in my ARM template and based on a condition, I want to ski the SB creation in a certain env.
Thanks for the Video Adam, can i put a condition before deploying something. The condition should implement checking if a specific tag is set, and if so it will proceed with a deployment.
If you have that resource specified in the template then you can use reference. [reference(parameters('storageAccountName'), '2016-12-01', 'Full').tags] Otherwise you can't refer to resources that are not in the template. In that case you powershell or cli.
@@AdamMarczakYT i dont think i can do it by referencing to specific resources. I have the following template which i am using: github.com/DeanCefola/Azure-Policy The Temlate activates Diagnostic Settings for a lot of different ressources. My Thought was to just put a if the tag"xy" is applied on a ressource --> run the template i attached above. Would be rly glad if u can help me there.
You don't need all these, just download the templates before you hit the create (do not download it when it's already created, it won't work because it got already other interfaces). You open the template (or use automation cli or devops), create new and add the templates (you only need the template.json), when you deploy, you edit the parameters and copy the parameters from the download parameter.json, then you deploy! crap!!!