Get-HubEntry - Progress bar - Hide

Hi,

I don't think there's a way right now to silence the progress bar.

Even though our secret management module is (source), it looks like the Hub PowerShell module used by this module is the culprit here.

I'll open a ticket and look into it.

We are writing a replacement module that will be integrated in our new Devolutions.PowerShell PS module. That new SecretManagement module will use our RDM backend to retrieve password. That means one module could fetch credentials from Hub, DVLS or any data source supposted by RDM throught the Secret Management interface. I'll make sure that new module also silence progress bar when asked to.

Regards

While you're at it, it would make a huge difference - if you could support the metadata concept from the secret management module. It is not supported at the moment.

I can add multiple entries, with the same logical name.

This leaves me with multiple entries, where I would like to have an error - that I already have an entry with the same name. If I want to overwrite the secret, I would expect to use the -Force option.

For now, the module fetches the first entry, based on the guid id of the different entries. So not even last in or first created. Please take that into consideration.

Are you talking about the information returned by Get-SecretInfo?

If so, what metadata would be useful?

The powershell concept is that you can add a HashTable, that would be appended directly to your secret entry. This would enable the end-user to add any semi-complex metadata structure. This can be all kind of things - so I wouldn't limit what types / structures you should. Honoring the HashTable would make people capable of handle any future scenario, and make it easier to migrate from other platforms.

I can add multiple entries, with the same logical name.

This leaves me with multiple entries, where I would like to have an error - that I already have an entry with the same name. If I want to overwrite the secret, I would expect to use the -Force option.

For now, the module fetches the first entry, based on the guid id of the different entries. So not even last in or first created. Please take that into consideration.

Hello Motz,

Adding multiple entries with the same name will be prevented.

The default behavior of Set-Secret is to overwrite the existing secret. To prevent this, the switch -NoClobber must be used. No Force switch will be implemented.

Get-SecretInfo will return unique names (group\name). However, it is possible to have two entries with the same name in the same group in Hub. In those case, we are considering returning the ID as the secret name. Get-Secret, Remove-Secret and Set-Secret will fail in those case.