registering a second vault may imply a different store

[JamesWTruher]

at least that's what I thought would happen. Here's a transcript:

S /> set-secret -name test1                                                                                                                                                                                                                                                                                cmdlet Set-Secret at command pipeline position 1                                                                                                      Supply values for the following parameters:                                                                                                           
SecureStringSecret: *************
Creating a new SecretStore vault. A password is required by the current store configuration.
Enter password:

Enter password again for verification:

PS /> get-secret test1
System.Security.SecureString
PS /> get-secret test1 -as
lsjkflkjsdlkf
PS /> get-secretinfo

Name          Type VaultName
----          ---- ---------
test1 SecureString SecretStore

PS /> Register-SecretVault -Name ss2 -ModuleName Microsoft.PowerShell.SecretStore                      
PS /> get-secretinfo                                                             

Name          Type VaultName
----          ---- ---------
test1 SecureString SecretStore
test1 SecureString ss2

I thought I was creating a second store, but it's the same. Is there a way to create a second vault with the same module?

[issue-label-bot[bot]]

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.81. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

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

[SydneyhSmith]

We determined that a users may want to use a vault extension multiple times with different configurations and different names so I will mark this as closed/by design