-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Conversation
If you're a MSFT employee, click this link |
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 |
Automation for azure-sdk-for-rubyNothing to generate for azure-sdk-for-ruby |
Can one of the admins verify this patch? |
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
The two APIs are used by exposure control. We are asked to add them into swagger for compliance requirement. |
Automation for azure-sdk-for-goA 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: |
Automation for azure-sdk-for-javaA 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: |
Automation for azure-sdk-for-nodeA 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: |
Automation for azure-sdk-for-jsThe initial PR has been merged into your service PR: |
...cation/datafactory/resource-manager/Microsoft.DataFactory/stable/2018-06-01/datafactory.json
Show resolved
Hide resolved
...cation/datafactory/resource-manager/Microsoft.DataFactory/stable/2018-06-01/datafactory.json
Outdated
Show resolved
Hide resolved
...cation/datafactory/resource-manager/Microsoft.DataFactory/stable/2018-06-01/datafactory.json
Outdated
Show resolved
Hide resolved
...cation/datafactory/resource-manager/Microsoft.DataFactory/stable/2018-06-01/datafactory.json
Outdated
Show resolved
Hide resolved
There was a problem hiding this 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": { |
There was a problem hiding this comment.
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)?
There was a problem hiding this comment.
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.
Approving from ARM side since its already present on service. Thanks for clarifying @hvermis |
@hovsepm Could you please merge this PR? |
@zhangyd2015 @anuchandy will review and merge it. |
@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. |
Azure#4958) * Add exposure control APIs. * Resolve reivew comments * Delete API ExposureControl_GetFeatureBySubscription * Resolve review comments
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:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.