Request: Register-SecretVault should call Test-SecretVault of the implementing extension in host UI Thread about secretmanagement

[issue-label-bot]

Issue-Label Bot is automatically applying the label feature_request to this issue, with a confidence of 0.74. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[SydneyhSmith]

Thanks we are going to close this as by design

[SydneyhSmith]

@JustinGrote we made the choice to separate the Testing of the vault from Registration in order to facilitate debugging (you may not want registration to fail just because the vault isnt currently available)...would love to hear more about why this would be useful though!

[JustinGrote]

@SydneyhSmith I feel this is something that can be left up to the extension author in = VaultParameters, for instance an extension can have "Offline" VaultParameter to skip parts of the check if that offline registration is required. Maybe instead of it calling Test-SecretVault directly it could be a separate function like Test-SecretVaultIsValid that is specifically related to that piece so test-secretvault still always assumes it is onlin

Otherwise my workaround is sufficient in that I just call Test-SecretVault at the top of every other function :)