Initial add of SR swagger spec #10220
Closed
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
[Staging] Swagger Validation Report
️✔️ |
| Rule | Message |
|---|---|
|
In operation "CreateKey", parameter vaultBaseUrl is required in the swagger spec but is not present in the provided example parameter values. Url: Microsoft.KeyVault/stable/7.0/keyvault.json#L13 |
|
In operation "SetCertificateIssuer", parameter parameter is required in the swagger spec but is not present in the provided example parameter values. Url: Microsoft.KeyVault/stable/7.0/keyvault.json#L1787 |
|
In operation "ImportKey", parameter vaultBaseUrl is required in the swagger spec but is not present in the provided example parameter values. Url: Microsoft.KeyVault/stable/7.0/keyvault.json#L13 |
|
In operation "DeleteKey", parameter vaultBaseUrl is required in the swagger spec but is not present in the provided example parameter values. Url: Microsoft.KeyVault/stable/7.0/keyvault.json#L13 |
|
In operation "UpdateKey", parameter vaultBaseUrl is required in the swagger spec but is not present in the provided example parameter values. Url: Microsoft.KeyVault/stable/7.0/keyvault.json#L13 |
|
In operation "GetKey", parameter vaultBaseUrl is required in the swagger spec but is not present in the provided example parameter values. Url: Microsoft.KeyVault/stable/7.0/keyvault.json#L13 |
|
In operation "GetKeyVersions", parameter vaultBaseUrl is required in the swagger spec but is not present in the provided example parameter values. Url: Microsoft.KeyVault/stable/7.0/keyvault.json#L13 |
|
In operation "GetKeys", parameter vaultBaseUrl is required in the swagger spec but is not present in the provided example parameter values. Url: Microsoft.KeyVault/stable/7.0/keyvault.json#L13 |
|
In operation "BackupKey", parameter vaultBaseUrl is required in the swagger spec but is not present in the provided example parameter values. Url: Microsoft.KeyVault/stable/7.0/keyvault.json#L13 |
|
In operation "RestoreKey", parameter parameters is required in the swagger spec but is not present in the provided example parameter values. Url: Microsoft.KeyVault/stable/7.0/keyvault.json#L428 |
️❌SemanticValidation: 1 Errors, 0 Warnings [Detail] [Expand]
❌| Rule | Message |
|---|---|
|
discriminator must be a required property. |
|
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-python
|
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
|
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
|
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-js
|
azure-sdk-for-go
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-net
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-java
|
|
Can one of the admins verify this patch? |
|
Azure Pipelines successfully started running 1 pipeline(s). |
2 similar comments
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
lmazuel
reviewed
Jul 28, 2020
.../schemaregistry/data-plane/Microsoft.EventHub/preview/2018-01-01-preview/schemaregistry.json
Outdated
Show resolved
Hide resolved
lmazuel
reviewed
Jul 28, 2020
.../schemaregistry/data-plane/Microsoft.EventHub/preview/2018-01-01-preview/schemaregistry.json
Outdated
Show resolved
Hide resolved
lmazuel
reviewed
Jul 28, 2020
.../schemaregistry/data-plane/Microsoft.EventHub/preview/2018-01-01-preview/schemaregistry.json
Outdated
Show resolved
Hide resolved
|
Azure Pipelines successfully started running 1 pipeline(s). |
7 similar comments
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This was referenced Jul 28, 2020
|
Azure Pipelines successfully started running 1 pipeline(s). |
arerlend
requested review from
brjohnstmsft,
giakas,
heaths,
hitenjava,
hyonholee,
jlichwa,
Kishp01,
kjeur,
matthchr,
MehaKaushik,
MikhailTryakhov,
novinc,
RandalliLama,
shahabhijeet,
shurd,
solankisamir,
stankovski,
Tiano2017,
TimLovellSmith,
tjacobhi,
v-Ajnava,
v-shhatt,
wilcobmsft,
xingwu1 and
yangyuan
as code owners
|
Comment was made before the most recent commit for PR 10220 in repo Azure/azure-rest-api-specs |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Closing for consistency in PR branch name. |
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.
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.