-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Create KeyVault.json #6975
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
Create KeyVault.json #6975
Conversation
Event definitions for Key Vault Certificates, Keys and Secrets - NewVersion, Near Expiry and Expired
In Testing, Please Ignore[Logs] (Generated from 44674ab, Iteration 12)
|
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
|
Can one of the admins verify this patch? |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
Change topic to vaultname
|
@jlichwa Hello. Why do we have this PR? I don't see any path referring these definitions. We cannot pass the Avocado's check. |
specification/eventgrid/data-plane/Microsoft.KeyVault/stable/2018-01-01/KeyVault.json
Outdated
Show resolved
Hide resolved
specification/eventgrid/data-plane/Microsoft.KeyVault/stable/2018-01-01/KeyVault.json
Show resolved
Hide resolved
kalyanaj
left a comment
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.
For consistency with the rest of the files under EventGrid dataplane, please consider removing the additional line spacing used in this file.
kalyanaj
left a comment
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.
For each definition name such as CertificateNewVersionCreated, KeyNearExpiry etc. since all the definitions share the same namespace Microsoft.EventGrid.Models, please add the KeyVault prefix, as an example, please rename CertificateNewVersionCreated to KeyVaultCertificateNewVersionCreated. This will help with better discoverability of all KeyVault specific event definitions. Also, typically, we use the "EventData" suffix for such event definitions (e.g. StorageBlobCreatedEventData), so please consider adding EventData suffix as well to each definition name. (for example "CertificateNewVersionCreated" would become KeyVaultCertificateNewVersionCreatedEventData.).
Remove empty lines
This reverts commit 66c7615.
|
Updated names KeyVault prefix and Event Data Suffix |
|
@jlichwa Can I assume that this PR is in progress and there will be another team working on the API paths later? |
Done |
|
@myronfanqiu Can we Merge based on comments? @kalyanaj |
|
@jlichwa I still don't understand the purpose of this PR. Who will use these definitions? |
It is for EventGridTeam( @kalyanaj ) as part of their OnBoarding process for new events schema. Based on that schema they will build API (they cannot do it without it) and once it is ready for Public Preview, it will be added to Readme.md as a part of API to customers. |
|
@myronfanqiu, please see my comment earlier in this PR (#6975 (comment)) for more context on how these definitions will be used. (FYI: @jlichwa). |
kalyanaj
left a comment
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.
LGTM.
|
@jilchwa One comment. You have created a new JSON file in this PR. But this file is never included in the readme.md file. So, no tests will be run on this file unless you actually include it. I believe the failed tests are really unrelated to your file. (which is a seperate discussion). But, first please include the file reference in the readme file. |
|
Remove the label |
|
@jlichwa Hello. Resolve the CI and I can merge this PR. |
Event definitions for Key Vault Certificates, Keys and Secrets - NewVersion, Near Expiry and Expired
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.