forked from Azure/azure-rest-api-specs
-
Notifications
You must be signed in to change notification settings - Fork 3
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
test purview #3545
Merged
Merged
test purview #3545
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Swagger Validation Report
|
compared swaggers (via Oad v0.9.6)] | new version | base version |
---|---|---|
2019-11-01-preview | 2019-11-01-preview(38b3d47) | 2019-11-01-preview(main) |
2021-07-01-preview | 2021-07-01-preview(38b3d47) | 2021-07-01-preview(main) |
️️✔️
Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️❌
LintDiff: 5 Errors, 0 Warnings failed [Detail]
The following errors/warnings are introduced by current PR:
Rule | Message |
---|---|
AutoRest exception |
"location":"specification/purview/data-plane/administration/readme.md", "tag":"package-composite-1", "details":"swagger-document/compose - FAILED" |
AutoRest exception |
"location":"specification/purview/data-plane/administration/readme.md", "tag":"package-composite-1", "details":"Error: The 'title' across provided OpenAPI definitions has to match. Found: 'DataPlaneAccountClient', 'Purview Metadata Policies Service REST API Document'. Please adjust or provide an override (--title=...)." |
AutoRest exception |
"location":"specification/purview/data-plane/readme.md", "tag":"package-2021-07-01-preview", "details":"swagger-document-override/md-override-loader - FAILED" |
AutoRest exception |
"location":"specification/purview/data-plane/readme.md", "tag":"package-2021-07-01-preview", "details":"Error: Could not read 'file:///mnt/vss/_work/1/azure-rest-api-specs/specification/purview/data-plane/Azure.Analytics.Purview.MetadataPolicies/preview/2021-07-01-preview/purviewMetadataPolicy.json'." |
AutoRest exception |
"location":"specification/purview/data-plane/readme.md", "tag":"package-2021-07-01-preview", "details":"swagger-document/loader - FAILED" |
️️✔️
[Staging] Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️❌
Avocado: 1 Errors, 0 Warnings failed [Detail]
Rule | Message |
---|---|
NO_JSON_FILE_FOUND |
The JSON file is not found but it is referenced from the readme file. readme: specification/purview/data-plane/readme.md json: Azure.Analytics.Purview.MetadataPolicies/preview/2021-07-01-preview/purviewMetadataPolicy.json |
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
ApiReadinessCheck succeeded [Detail] [Expand]
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️
PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️
[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
[Staging] SDK Track2 Validation succeeded [Detail] [Expand]
Validation passes for SDKTrack2Validation
- The following tags are being changed in this PR
- "https://github.com/openapi-env-test/azure-rest-api-specs/blob/38b3d47203d197c01c3e03961617ad2a302595aa/specification/purview/data-plane/administration/readme.md#tag-package-composite-1">purview/data-plane/administration/readme.md#package-composite-1
- "https://github.com/openapi-env-test/azure-rest-api-specs/blob/38b3d47203d197c01c3e03961617ad2a302595aa/specification/purview/data-plane/readme.md#tag-package-2021-07-01-preview">purview/data-plane/readme.md#package-2021-07-01-preview
️️✔️
CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
Swagger Generation Artifacts
|
Swagger pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment. |
This was referenced Jul 22, 2022
Closed
[AutoPR Azure.Analytics.Purview.Administration] test purview
openapi-env-test/azure-sdk-for-net#1124
Closed
Closed
Closed
/azp run |
No pipelines are associated with this pull request. |
This was referenced Jul 25, 2022
Closed
Closed
azure-sdk
pushed a commit
that referenced
this pull request
Aug 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following appy to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.
Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
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 any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.