Skip to content

Upgrade Azure.Security.KeyVault.Secrets to use KeyVaultSecretIdentifier.Parse() for KeyVault reference URI validation #222

Closed

Description

I see we should start using KeyVaultSecretIdentifier.Parse. Since this next release will be adding a new API, and bumping a minor version. It will probably be a good candidate release for us to bump to Azure.Security.KeyVault.Secrets 4.1.0 to use this API.

We have no need to document the URI format. We shouldn't be aware of it.

Originally posted by Jimmy Campbell (@jimmyca15) in #210 (comment)

Activity

  1. avanigupta commented on Dec 10, 2020

    @avanigupta
    MemberAuthor

    KeyVaultSecretIdentifier.Parse is only available in preview release right now. We can update this as soon as 4.2.0 package is released for Azure.Security.KeyVault.Secrets.

  2. avanigupta commented on Aug 19, 2021

    @avanigupta
    MemberAuthor

    Azure.Security.KeyVault.Secrets v4.2.0 was released but it doesn't have the original KeyVaultSecretIdentifier.TryParse API. Tracking this feature request for Key Vault SDK team to add it again.

  3. avanigupta commented on Aug 29, 2022

    @avanigupta
    MemberAuthor

    Azure.Security.KeyVault.Secrets 4.3.0 version contains the required API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions