Skip to content
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

Merged
merged 1 commit into from
Dec 7, 2018

Conversation

sirajudeens
Copy link
Contributor

@sirajudeens sirajudeens commented Oct 22, 2018

…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

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@lmazuel lmazuel self-assigned this Oct 22, 2018
@lmazuel lmazuel self-requested a review October 22, 2018 18:16
@lmazuel lmazuel added the DoNotMerge <valid label in PR review process> use to hold merge after approval label Oct 22, 2018
@AutorestCI
Copy link

AutorestCI commented Oct 22, 2018

Automation for azure-sdk-for-js

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-js#630

@AutorestCI
Copy link

AutorestCI commented Oct 22, 2018

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#3668

@AutorestCI
Copy link

AutorestCI commented Oct 22, 2018

Automation for azure-sdk-for-node

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-node#4240

@AutorestCI
Copy link

AutorestCI commented Oct 22, 2018

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#3645

@lmazuel
Copy link
Member

lmazuel commented Nov 30, 2018

@AutorestCI rebuild

@AutorestCI
Copy link

AutorestCI commented Nov 30, 2018

Automation for azure-sdk-for-ruby

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-ruby#1986

@AutorestCI
Copy link

AutorestCI commented Nov 30, 2018

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

@salameer
Copy link
Member

salameer commented Dec 6, 2018

once ARM acks here we can move forward

@salameer
Copy link
Member

salameer commented Dec 6, 2018

@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": {
Copy link
Contributor

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

  1. a VMSS is PUT with provisionAfterExtension, as specified in this version,
  2. 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?

Copy link
Contributor Author

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.

Copy link
Contributor

@KrisBash KrisBash left a 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

@KrisBash KrisBash added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Dec 7, 2018
@veronicagg
Copy link
Contributor

thanks @KrisBash . Merging per @lmazuel previous review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review DoNotMerge <valid label in PR review process> use to hold merge after approval Reassign
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants