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 exposure control APIs according to the ARM compliance requirement. #4958

Merged
merged 4 commits into from
Jan 16, 2019
Merged

Add exposure control APIs according to the ARM compliance requirement. #4958

merged 4 commits into from
Jan 16, 2019

Conversation

zhangyd2015
Copy link
Contributor

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-portal-comment
Copy link

If you're a MSFT employee, click this link
to view this PR's validation status on our new OpenAPI Hub spec management tool.

@azuresdkci
Copy link
Contributor

Hello!!

The Rest API Specs team wishes everyone a happy holiday and would like to kindly inform you that responses and review to Pull request will be delayed during the holiday period (now -> 2nds of January) to allow for Awesome reviewers to have an awesome time with their families during the holidays!

Thanks and Have a WONDERFUL HOLIDAY

@AutorestCI
Copy link

AutorestCI commented Dec 22, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@AutorestCI
Copy link

AutorestCI commented Dec 22, 2018

Automation for azure-sdk-for-python

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

@zhangyd2015
Copy link
Contributor Author

The two APIs are used by exposure control. We are asked to add them into swagger for compliance requirement.

@AutorestCI
Copy link

AutorestCI commented Dec 22, 2018

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#3865

@AutorestCI
Copy link

AutorestCI commented Dec 22, 2018

Automation for azure-sdk-for-java

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-java#2136

@AutorestCI
Copy link

AutorestCI commented Dec 22, 2018

Automation for azure-sdk-for-node

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-node#4190

@AutorestCI
Copy link

AutorestCI commented Dec 22, 2018

Automation for azure-sdk-for-js

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

@zhangyd2015 zhangyd2015 changed the title Add exposure control APIs according to the compliance request. Add exposure control APIs according to the ARM compliance requirement. Dec 22, 2018
@hovsepm hovsepm added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Dec 26, 2018
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.

@zhangyd2015 please take a look at the comment. I am not sure if I understand this API.

@@ -156,6 +156,54 @@
}
}
},
"/subscriptions/{subscriptionId}/providers/Microsoft.DataFactory/locations/{locationId}/getFeatureValue": {
Copy link
Contributor

Choose a reason for hiding this comment

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

What is the usecase for this API? Is it doing something similar to Azure Feature Exposure Control (AFEC)?

Copy link
Contributor

Choose a reason for hiding this comment

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

@ravbhatnagar ADF doesn't use Azure Feature Exposure Control, instead we have our own implemented in our backend which controls some throttling limits and enabled disabled features for the customer, and this API is allowing the user to query for a specific value.

@ravbhatnagar
Copy link
Contributor

Approving from ARM side since its already present on service. Thanks for clarifying @hvermis

@ravbhatnagar ravbhatnagar added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed ARMReviewInProgress WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Jan 10, 2019
@zhangyd2015
Copy link
Contributor Author

@hovsepm Could you please merge this PR?

@hovsepm
Copy link
Contributor

hovsepm commented Jan 15, 2019

@zhangyd2015 @anuchandy will review and merge it.

@anuchandy
Copy link
Member

anuchandy commented Jan 16, 2019

@zhangyd2015 @hvermis - There are couple of model validation errors. They are not introduced in this PR so not a blocker to merge. Please ensure to triage those. I will create an issue.

@anuchandy anuchandy merged commit b42820a into Azure:master Jan 16, 2019
TalluriAnusha pushed a commit to AsrOneSdk/azure-rest-api-specs that referenced this pull request Feb 6, 2019
Azure#4958)

* Add exposure control APIs.

* Resolve reivew comments

* Delete API ExposureControl_GetFeatureBySubscription

* Resolve review comments
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 review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants