-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
VMSS: exposing the requireGuestProvisionSignal
field for 2019-03-01
#7246
Conversation
In Testing, Please Ignore[Logs] (Generated from 69cac3e, Iteration 4).NET: test-repo-billy/azure-sdk-for-net [Logs] [Diff]
Python: test-repo-billy/azure-sdk-for-python [Logs] [Diff]
Java: test-repo-billy/azure-sdk-for-java [Logs] [Diff]JavaScript: test-repo-billy/azure-sdk-for-js [Logs] [Diff]
Go: test-repo-billy/azure-sdk-for-go [Logs] [Diff]
Ruby: test-repo-billy/azure-sdk-for-ruby [Logs] [Diff]
|
Can one of the admins verify this patch? |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
specification/compute/resource-manager/Microsoft.Compute/stable/2019-03-01/compute.json
Show resolved
Hide resolved
Signing off frm ARM side. Since this property has existed on the service side in this api-version. |
hi @tombuildsstuff could you pls fix CI failure then the PR could be merged? |
@yungezz unfortunately that link returns a 404: |
@tombuildsstuff don't worry, we're trying to find a public place for the doc. |
offline version for reference. |
hi @tombuildsstuff any update on the PR? |
HI @tombuildsstuff could you pls fix CI failure? |
0e60fa1
to
69cac3e
Compare
@tombuildsstuff ,
|
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.
Noticed this field was being sent across the wire but isn't in the Swagger: