-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Microsoft.insights pl flags new version - fix conflicting parameters for SDK #8905
Microsoft.insights pl flags new version - fix conflicting parameters for SDK #8905
Conversation
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
Azure Pipelines successfully started running 1 pipeline(s). |
Can one of the admins verify this patch? |
azure-sdk-for-go - Release
|
azure-sdk-for-java - Release
|
azure-cli-extensions - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-js - Release
|
azure-sdk-for-python - Release
|
azure-sdk-for-net - Release
|
Azure Pipelines successfully started running 1 pipeline(s). |
@akning-ms Hi. This PR changed the three common parameters(sub, api and resource group) by using the common type. Only the descriptions and validation part changed. Since they are quite general parameters across Azure and these validations have been there before this PR. I think it's not a real breaking change for customer. Could you take a look and help us merge this PR? |
…for SDK (Azure#8905) * clone to new version for new flags * Update readme.md * Update readme.md * Update components_API.json * Update components_API.json * Update componentProactiveDetection_API.json * Update ProactiveDetectionConfigurationUpdate.json
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.