Delete throws error if secret doesn't exist

[lukos]

It is not clear how to delete a secret that might not exist. In most cases, I would definitely expect the default behaviour not to throw an exception if the secret does not exist but at worst, there should be an overload that allows us to ignore the error. Throwing an error means that for every delete, I either need to call GetSecret first or catch and ignore the exception which is nasty.

Also, the link to log a problem about "This Product" is broken.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 2b378d7c-6191-9f15-6c34-30c4bfbcb5a5
• Version Independent ID: 3fafa4d7-15a9-82dc-669a-f9e3b61a9065
• Content: SecretClient.StartDeleteSecretAsync(String, CancellationToken) Method (Azure.Security.KeyVault.Secrets) - Azure for .NET Developers
• Content Source: xml/Azure.Security.KeyVault.Secrets/SecretClient.xml
• Service: azure
• GitHub Login: @rloutlaw
• Microsoft Alias: routlaw

[jsquire]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[heaths]

@rloutlaw could you look into the "This Product" link at the bottom. It's 404'ing.

[heaths]

As for the change request, we could add a DeleteIfExists like we've done in other libraries including Storage. Newer libraries shouldn't throw on delete by default, but the pattern wasn't established for older ones.

That said, we are working on some new features we could take advantage of instead, but are not yet available - should be early next year. We can't change the existing method behavior, though, as that would be a breaking change.

[heaths]

Note to self: we'd want to specifically handle the case where the initial delete request already 404'd e.g., here. Could also do it in the caller but would then have to duplicate. If we don't mark the operation already-completed, UpdateStatus() would effectively run forever.

[github-actions]

Hi @lukos, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.

[github-actions]

Hi @lukos, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.