[KeyVault] - Add release policy grammar links #20941
Merged
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
ghost
added
the
maorleger
changed the title
sadasant
approved these changes
Mar 18, 2022
heaths
reviewed
Mar 18, 2022
| /** | ||
| * The policy rules under which the key can be released. Encoded based on the {@link KeyReleasePolicy.contentType}. | ||
| * | ||
| * For more information regarding the release policy grammar for Azure Key Vault, please refer to: |
There was a problem hiding this comment.
"grammar" works, but I wonder if "schema" would be better. It's more oft used. Either is fine, though.
heaths
approved these changes
Mar 18, 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.
Packages impacted by this PR
@azure/keyvault-keys
Issues associated with this PR
#18400
Describe the problem that is addressed by this PR
The service team would like to document the release policy grammar, and as such
has asked us to link to their documentation. While the documentation is not live
yet, I did get the content folks to point it to a valid url so that we can
include it in our doc-comments now.
Checklists