Explore using Azure.Core for KeyVaultSetting

[heaths]

Currently, we plan to ship KeyVaultSetting as an immutable type so that we can better control what values we accept as input (output/response is open) since we need to set the type. For GA, we should explore using Azure.Value (source) which is basically like a COM VARIANT.

If we did that, we could make KeyVaultSetting mutable but need to make sure that the user doesn't change the Value type. Ultimately, it won't much matter since the service won't allow changing the type anyway. Also, the typed stored has to be serializable as a string.

[pallavit]

@heaths Is this something we still want to explore for GA given we are mostly code-complete?

[heaths]

That's more of a question for @KrzysztofCwalina and @tg-msft. Are we ready to push Azure.Value to Azure.Core GA?

[KrzysztofCwalina]

I would love to move it to Azure.Core, but we cannot just push it. We need to: a) identify scenarios we need to support, b) validate that it works in scenarios we want it to work, c) go through arch review.

[pallavit]

Do we have a tracking issue to evaluate Azure.Value for Azure.Core?

[heaths]

I don't see anything currently. @KrzysztofCwalina is there anything tracking release of Azure.Value?

[KrzysztofCwalina]

I don't think we have anything.

[heaths]

Tracking in #32978. I optimistically added it to the 2023-01 milestone. Feel free to update pragmatically.

[heaths]

KeyVaultSetting GA'd, so this is no longer relevant.