Skip to content
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

[KeyVault] - Clean up sample key deletion #18574

Merged
merged 1 commit into from
Nov 9, 2021

Conversation

maorleger
Copy link
Member

What

  • Skip deleting keys in every sample
  • Delete the purgeAllKeys sample
  • Add an example on how to delete and purge a single key

Why

Deleting and purging keys is a costly operation in terms of time. There's no
reason to wait for deleting and purging every single key when we run the
samples now that we deploy and tear down key vaults per test run.

@maorleger maorleger requested a review from sadasant as a code owner November 8, 2021 19:00
@ghost ghost added the KeyVault label Nov 8, 2021
Copy link
Contributor

@sadasant sadasant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was concerned that keeping keys in an account would be costly, but Maor helped me see that KeyVault charges per number of operations, so this change makes a lot of sense!

@maorleger
Copy link
Member Author

/azp run js - keyvault-keys - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@maorleger
Copy link
Member Author

Known issues with re-installing native dependencies on ubuntu. Since there's no product changes and the samples are passing I am merging

@maorleger
Copy link
Member Author

/check-enforcer override

@maorleger maorleger merged commit fab3ed3 into Azure:main Nov 9, 2021
@maorleger maorleger deleted the stop-deleting-keys branch November 9, 2021 17:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants