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

Remove ReplicaSet Nested Resource #7627

Merged
merged 2 commits into from
Oct 29, 2019
Merged

Remove ReplicaSet Nested Resource #7627

merged 2 commits into from
Oct 29, 2019

Conversation

jihochang
Copy link
Contributor

@jihochang jihochang commented Oct 24, 2019

ReplicaSet is not a public feature and there are no customers using it. It was an internal prototype that we are now removing (behind a feature flag).

I have reviewed the ReplicaSets change with Gaurav Bhatnagar, Chris Eggert, and Anthony Martin.

Let me know if you have any questions.

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:

  • 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.

@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Oct 24, 2019

In Testing, Please Ignore

[Logs] (Generated from a7ad452, Iteration 8)

Warning .NET: test-repo-billy/azure-sdk-for-net [Logs] [Diff]
  • No packages generated.
Succeeded Go: test-repo-billy/azure-sdk-for-go [Logs] [Diff]
Warning JavaScript: test-repo-billy/azure-sdk-for-js [Logs] [Diff]
  • Warning @azure/arm-domainservices [Logs]

@AutorestCI
Copy link

AutorestCI commented Oct 24, 2019

Automation for azure-sdk-for-go

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

@jihochang
Copy link
Contributor Author

Adding WaitForARMFeedback #7064

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

Copy link
Member

@raych1 raych1 left a comment

Choose a reason for hiding this comment

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

Removing API from existed version is breaking change.

@anthony-c-martin
Copy link
Member

Removing API from existed version is breaking change.

Note that this feature has always been in private preview - from an ARM perspective, I'm fine with making this change.

@anthony-c-martin anthony-c-martin added the ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review label Oct 25, 2019
Copy link
Member

@anthony-c-martin anthony-c-martin 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 - assuming you'll be addressing #7627 (comment).

@jihochang
Copy link
Contributor Author

Fixed the readonly property issue.

@jihochang
Copy link
Contributor Author

@raych1 Could you complete the merge?

@raych1 raych1 self-requested a review October 29, 2019 03:01
@raych1 raych1 merged commit d438fff into Azure:master Oct 29, 2019
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.

5 participants