[KeyVault] Migrate keyvault-certificates to new recorder #22575
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
|
API change check API changes are not detected in this pull request. |
timovv
requested review from
HarshaNalluru,
deyaaeldeen,
joheredi and
jeremymeng
HarshaNalluru
approved these changes
Jul 21, 2022
joheredi
approved these changes
Jul 25, 2022
|
Re-skipping the timeout tests for now since it seems like we have some weird race condition going on where tests fail sometimes in CI. |
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-certificatesIssues associated with this PR
Migrates keyvault-certificates to the new recorder. Fairly straightforward.