Make live managed identity tests independent of soft delete #10879
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.
When soft delete is enabled for the Key Vault used by these tests, the second case executed will fail because it tries to set and delete a secret deleted by the first case executed. When these tests were written soft delete was disabled by default on new Key Vaults. Now it's enabled by default.
It doesn't matter which Key Vault operation the tests attempt because the purpose is to validate the access token acquired by the credential. The simple fix here is to list the vault's secrets. This eliminates problems due to the state of the Vault's secrets (and requires authorization even when the vault has none).