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

Compute Swagger spec update :- Add the missing PATCH for VmssExtension operation #7724

Merged
merged 12 commits into from
Nov 18, 2019

Conversation

srinath9795
Copy link
Contributor

Latest improvements:

Added the missing PATCH support for the VMSSExtension operation in the Compute Swagger spec.

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Contribution checklist:

  • I have reviewed the documentation for the workflow.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.
  • The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

  • Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
  • adding/removing APIs.
  • adding/removing properties.
  • adding/removing API-version.
  • adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

  • If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
    Please follow the link to find more details on API review process.

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@AutorestCI
Copy link

AutorestCI commented Nov 6, 2019

Automation for azure-sdk-for-python

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-python#8691

@srinath9795 srinath9795 changed the title Swagger spec update :- Add the missing PATCH for VmssExtension operation Compute Swagger spec update :- Add the missing PATCH for VmssExtension operation Nov 6, 2019
@AutorestCI
Copy link

AutorestCI commented Nov 6, 2019

Automation for azure-sdk-for-go

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-go#6375

@lirenhe lirenhe added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Nov 11, 2019
@hyonholee
Copy link
Contributor

LGTM

}
}
},
"x-ms-long-running-operation": true
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As this is a long running operation, is it better to return 202 instead of 200?

Copy link
Contributor Author

@srinath9795 srinath9795 Nov 14, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see that for all the other existing resources (VM, VMSS, AvSet, Image, VMExtension..) as well, only 200 (OK) is specified in the spec.

But from the code, and as CRP treats "patch" & "put" the same way -- added 201 (Created) as well.

@hyonholee to help confirm as well.

Copy link
Contributor

@ravbhatnagar ravbhatnagar 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 from ARM side barring the one feedback which is to consider adding 202 or 201 (with non-terminal provisioning state) to indicate its long running operation

@ravbhatnagar ravbhatnagar 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 Nov 14, 2019
@lirenhe
Copy link
Member

lirenhe commented Nov 15, 2019

@srinath9795, please let me know if the code is ready to merge.

@srinath9795
Copy link
Contributor Author

@srinath9795, please let me know if the code is ready to merge.

@lirenhe - Yes, the changes for this PR are ready to be merged. Thanks!

@lirenhe lirenhe merged commit 0a7f5e5 into Azure:master Nov 18, 2019
TalluriAnusha pushed a commit to AsrOneSdk/azure-rest-api-specs that referenced this pull request Dec 11, 2019
…n operation (Azure#7724)

* Swagger spec update :- Add the missing PATCH for VmssExtension operation

* remove name

* another try by adding back name with "readonly". I guess, a 3rd commit may be required (with readonly for type)

* Added "readOnly": true for type

* add type explicitly in VMSSExtension & Vmss Extension Update.

* Make the publisher & type "readonly" in the VirtualMachineScaleSetExtensionUpdateProperties

* just use VirtualMachineScaleSetExtensionProperties

* Add 201 as well.
@CecileRobertMichon
Copy link
Contributor

Hi @lirenhe @ravbhatnagar, this PR introduced a breaking change for AKS. See Azure/aks-engine#2605 for details. TLDR: we were relying on Go struct embedding of Type inside VirtualMachineScaleSetExtensionProperties. After this change, setting extension.Type will not work anymore since a new Type field was added in VirtualMachineScaleSetExtension.
cc @devigned @jackfrancis @AbelHu

@devigned
Copy link
Member

@jhendrixMSFT, have you seen this issue? It's a pretty gnarly one for Golang in particular.

@jhendrixMSFT
Copy link
Member

@devigned thanks for bringing this up. It highlights how model flattening is not version-resilient. FYI I've been considering removing this anonymous embedding in track 2, I think this example strengthens the case.

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants