-
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
LogAnalytics: update readme and fix conflicts by autorest.java #11126
Conversation
[Staging] Swagger Validation Report
❌ |
Rule | Message |
---|---|
1006 - RemovedDefinition |
The new version is missing a definition that was found in the old version. Was 'LinkedStorageAccounts' removed or renamed? New: Microsoft.OperationalInsights/preview/2019-08-01-preview/OperationalInsights.json#L425:3 Old: Microsoft.OperationalInsights/preview/2019-08-01-preview/OperationalInsights.json#L425:3 |
️❌
LintDiff: 1 Errors, 0 Warnings [Detail] [Expand]
❌
Rule | Message |
---|---|
AutoRest Exception |
"details":" "Channel": "fatal", "Text": "swagger-document/compose - FAILED" "Channel": "fatal", "Text": "Error: '$.parameters.SubscriptionIdParameter.description' has incompatible values (---\nThe workspace's resource subscription ID.\n, ---\n>-\n Gets subscription credentials which uniquely identify Microsoft Azure\n subscription. The subscription ID forms part of the URI for every service\n call.\n)."(node:5841) UnhandledPromiseRejectionWarning: Error: '$.parameters.SubscriptionIdParameter.description' has incompatible values (---The workspace's resource subscription ID.", "location":"https://github.com/Azure/azure-rest-api-specs/blob/fa184e5e2ffd1abd1cab37811730ecfae9ed2542/specification/operationalinsights/resource-manager/readme.md" |
️️✔️
Avocado [Detail]
️✔️
Validation passes for Avocado.
️️✔️
ModelValidation [Detail]
️✔️
Validation passes for ModelValidation.
️️✔️
SemanticValidation [Detail]
️✔️
Validation passes for SemanticValidation.
Azure Pipelines successfully started running 1 pipeline(s). |
Azure CLI Extension Generation
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-go
|
azure-sdk-for-java
|
azure-sdk-for-net
|
azure-sdk-for-python-track2
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
|
Trenton Generation
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
|
/azp run unifiedPipeline |
No pipelines are associated with this pull request. |
Hi, @xccc-msft. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
Hi, @xccc-msft. The PR will be closed since the PR has no update for 28 days. If you still need the PR review to proceed, please reopen it and @ mention PR assignee @myronfanqiu, @akning-ms. |
Hi, @xseeseesee. The PR has be closed for a long time and it's related branch still exist. If no further used for over 14 days, I will delete this related branch. Please tell me if you still need this branch. |
Hi, @xseeseesee. The PR has be closed for a long time and it's related branch still exist. Please tell me if you still need this branch or i will delete it in 14 days. |
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.
Please follow the link to find more details on PR review process.