-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Armory issues with snippets #1721
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How do we test the json updates which seem to be quite extensive? I'm presuming these would need to be updated in the storage account as well once this is merged?
} | ||
], | ||
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#", | ||
"contentVersion": "1.0.0.0", | ||
"variables": { | ||
//Insert here: variable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these comments expected to be removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't matter, they're testing artifacts and are removed before baseline comparison anyway.
Lifted new VM snippets from our documentation, kept it simple by not having any tabstops or placeholders. In general they're going to want parameters for these types of things anyway.
For virtual networks, made fixes in situ. The rest is mostly testcase baseline updates.