-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Adding provisionAfterExtensions property for ex… #4306
Conversation
Can one of the admins verify this patch? |
Automation for azure-sdk-for-jsThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-nodeThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
@AutorestCI rebuild |
Automation for azure-sdk-for-rubyThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-javaNothing to generate for azure-sdk-for-java |
once ARM acks here we can move forward |
@veronicagg, @lmazuel has already reviewed this one and was waiting for service to go live. once ARM acks please move forward. |
@@ -7067,6 +7067,13 @@ | |||
"readOnly": true, | |||
"type": "string", | |||
"description": "The provisioning state, which only appears in the response." | |||
}, | |||
"provisionAfterExtensions": { |
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.
Out of curiosity, what is the service behavior if
- a VMSS is PUT with provisionAfterExtension, as specified in this version,
- a lower-version client does a GET & PUT without provisionAfterExtension specified
Is the property wiped out, is the PUT failed, or is the prior value preserved(merge)? Does the behavior cause undesired effects?
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.
The lower-version client will not receive the property in GET operation, since the property has been introduced in 2018-06-01 onwards.
When there is a PUT operation with out this property, CRP will assume the property value is unmodified. This is the case with any other property.
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.
Signing off for ARM. One comment
…tension sequencing
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-version
in the path should match theapi-version
in the spec).Quality of Swagger