SydneyhSmith
commented
4 years ago @JustinGrote we think this could be a great idea, but we want to have more discussion on how the field would work...would a tags field make more sense?
Open JustinGrote opened 4 years ago
SydneyhSmith
commented
4 years ago @JustinGrote we think this could be a great idea, but we want to have more discussion on how the field would work...would a tags field make more sense?
Summary of the new feature/enhancement
As a powershell user, I sometimes want some more information about what a secret is for, and a provider may be able to provide that additional information in a way that I can programatically query/filter that information.
For example:
Proposed technical implementation details (optional)
Add a
[Object]property to Get-SecretInfo output (currently a [PSCustomObject], it should be more strongly typed).Some name possibilities: Notes, Description, Metadata
The provider can populate this property with additional information about the secret. This information would be provider specific and the provider can supply any type of object as long as it has a clean ToString() method to convert it. Most providers may just do a simple string description, others may submit a nested hashtable with properties like created, modified, etc.
Future: Some natural commonalities like "LastModified","Comment" may become common and should be added to the [SecretInfo] class designation to standardize them, however this property allows providers to deliver their own extensible information that's important to their provider.