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

Add managementGroups/{id}/descendants route to allow pagination of descendants #5917

Merged
merged 3 commits into from
Jun 17, 2019

Conversation

daxfohl
Copy link
Contributor

@daxfohl daxfohl commented May 10, 2019

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.

@AutorestCI
Copy link

AutorestCI commented May 10, 2019

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link

AutorestCI commented May 10, 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#5673

@AutorestCI
Copy link

AutorestCI commented May 10, 2019

Automation for azure-sdk-for-js

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-js#3844

@AutorestCI
Copy link

AutorestCI commented May 10, 2019

Automation for azure-sdk-for-go

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

@AutorestCI
Copy link

AutorestCI commented May 10, 2019

Automation for azure-sdk-for-java

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

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@azuresdkci azuresdkci requested a review from jhendrixMSFT May 10, 2019 22:36
adxsdknet added a commit to adxsdknet/azure-sdk-for-net that referenced this pull request May 10, 2019
REST Spec PR 'Azure/azure-rest-api-specs#5917'
REST Spec PR Author 'daxfohl'
REST Spec PR Last commit
@adxsdknet
Copy link

Automation for azure-sdk-for-net

A PR has been created for you:
Azure/azure-sdk-for-net#6245
.NET SDK Commits:
adxsdknet/azure-sdk-for-net@f54798f

@daxfohl
Copy link
Contributor Author

daxfohl commented May 13, 2019

ARM docs say to do the review before updating manifest. Here says functionality has to be available before review. Everywhere says please make sure API is approved before implementing. I'm confused.

@daxfohl
Copy link
Contributor Author

daxfohl commented May 13, 2019

Reviewing the documentation more, it seems like I should create a new api-version since it adds a new route. Is this correct?

@jhendrixMSFT jhendrixMSFT added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label May 14, 2019
@jhendrixMSFT
Copy link
Member

You only need to create a new API version if you're introducing breaking changes which doesn't appear to be the case here.
We cannot merge this PR until the API has been deployed, however we can review it here along with ARM's review.

@jhendrixMSFT
Copy link
Member

@daxfohl is this API live or still waiting ARM review?

@daxfohl
Copy link
Contributor Author

daxfohl commented May 20, 2019 via email

@sanjaiganesh sanjaiganesh 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 May 31, 2019
@sanjaiganesh
Copy link
Contributor

signed off after discussing with Gaurav.

@jhendrixMSFT
Copy link
Member

@daxfohl is this new endpoint live?

@daxfohl
Copy link
Contributor Author

daxfohl commented Jun 3, 2019 via email

@jhendrixMSFT jhendrixMSFT added the DoNotMerge <valid label in PR review process> use to hold merge after approval label Jun 6, 2019
@jhendrixMSFT
Copy link
Member

@daxfohl has this been resolved?

@daxfohl
Copy link
Contributor Author

daxfohl commented Jun 17, 2019 via email

@jhendrixMSFT jhendrixMSFT removed the DoNotMerge <valid label in PR review process> use to hold merge after approval label Jun 17, 2019
@jhendrixMSFT jhendrixMSFT merged commit 7f48731 into Azure:master Jun 17, 2019
@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Jun 17, 2019

SDK Automation [Logs] (Generated from f41247d)

Pending Python: Azure/azure-sdk-for-python
  • Package generation pending.
Pending Java: Azure/azure-sdk-for-java
  • Package generation pending.
Pending Go: Azure/azure-sdk-for-go
  • Package generation pending.
Pending JavaScript: Azure/azure-sdk-for-js
  • Package generation pending.

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.

6 participants