You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We noticed that when you have an existing secret and you need to create a new version of it you are required to re-enter the ContentType and Tags if you want to keep them. This seems like a very un-needed step to take when updating your secret and can be a lot of work if you have many tags like we do.
Expected Behavior: Tags and Content Type carries over for new version of existing secret
Actual Behavior: You are required to enter in your Content Type and Tags again when creating new version of existing secret.
The text was updated successfully, but these errors were encountered:
I've been using keyvault for a while now and just started running into this issue myself the last week. I don't remember having this issue in the past when interacting with keyvault. I'm pretty sure tags used to auto fill when creating a new version of a secret that already had tags. It would be good to get someone from the MS team to confirm if there has been a change recently. I haven't found anything in docs or online about this behaviour.
We noticed that when you have an existing secret and you need to create a new version of it you are required to re-enter the ContentType and Tags if you want to keep them. This seems like a very un-needed step to take when updating your secret and can be a lot of work if you have many tags like we do.
Expected Behavior: Tags and Content Type carries over for new version of existing secret
Actual Behavior: You are required to enter in your Content Type and Tags again when creating new version of existing secret.
The text was updated successfully, but these errors were encountered: