-
Hi, How do i add multiple subscriptions ? do i need to have multiple ARM template file and parameters file each per subscriptions or can i have one arm template file and one parameters file with multiple values for subscriptions? or can i have newsub.json and newsub.paramters.json, with the values for sub1 and sub2 specified in newsub.parameters.json ? thanks |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
Hi if I understand your scenario correctly you are looking at using AzOps to create new subscriptions. Yes you could have multiple subscriptions created from single |
Beta Was this translation helpful? Give feedback.
-
Thanks for the answer. Solution with the copy function looks good. I have another question though. My intention is not to create multiple subscription in one go. With one PR, I expect to create only a single subscription. I want to maintain the subscription values in the parameter file so that i can see the changes to the file in the history. With the copy function, say if the first two subscriptions are created today, can i use the same file and and the values for the third subscription in the same file so that when the pr is merged, it creates only the third subscription as the first two subscriptions were already created previously. With your first suggestion to replace the value of subscriptionAliasName with each PR, I need to keep previous subscriptionAliasName also in the same file so that i have the history of the changes. Is there a way to keep the previous subscriptionAliasName also in the same file and to add the new subscriptionAliasName so that PR will not fail as one of the subscriptionAliasName already exists? Thanks again |
Beta Was this translation helpful? Give feedback.
-
Yes, you can keep appending parameters with each pull request. ARM templates are idempotent, which means you can deploy the same template many times and get the same resource types in the same state. |
Beta Was this translation helpful? Give feedback.
Yes, you can keep appending parameters with each pull request. ARM templates are idempotent, which means you can deploy the same template many times and get the same resource types in the same state.