Open Callidus2000 opened 1 year ago
For other devs who want to create a new extension: I've included a workaround in my template module and in the corresponding ReadMe.
Returned secrets of type Hashtable also comeback as Case Sensitive, regardless of the vault implementation, I'm not sure if this is intended design or not now considering it's possible for a vault to be case sensitive.
If this is the case, I think it should be up to the Vault author to enforce the behavior.
Prerequisites
Steps to reproduce
Register a new secret vault, vaultparameter for the database lowercase in one case, CamelCase the second time
The vaultparameters are automatically provided to the extension via the
[hashtable]$AdditionalParameters
param.Within the extension the provided hashtable uses case sensitive keys. E.g.
fails for vault HashTableBugVault2.
A demo repository exists at https://github.com/Callidus2000/SecretManagement.HashTableBugs
Expected behavior
Actual behavior
Error details
No response
Environment data
Version
None
Visuals
No response