Hi
I have a problem with cmdlet get-VaultSecret and others that try to use Get-Vault function:

PS❯ get-VaultSecret

Get-Vault: C:\Program Files\WindowsPowerShell\Modules\PSVault\1.0.1\PSVault.psm1:2240
Line |
2240 |          $VaultObject  = $(Get-Vault -Address $APIAddress -Token $env: …
     |                            ~~~~~~~~~
     | The term 'Get-Vault' is not recognized as a name of a cmdlet, function, script file, or
     | executable program. Check the spelling of the name, or if a path was included, verify
     | that the path is correct and try again.

As think as I understand it necessary to use function get-Vaultobject

In this code:

begin{
        if($Address -notlike "http://*.*.*.*:8200"){$Address = "http://127.0.0.1:8200" }
    }

 process{
        $vaultobject = [PSCustomObject]@{'uri'= $Address + $prefix
                            'auth_header' = @{'X-Vault-Token'=$Token}
                            } 
    }
    end{
        return  $vaultobject
    }

You are assuming that the Vault is on port 8200. If anyone installs Hashicorp Vault on another port, this module will never work.
Ours is installed at a URL like this: https://hashivault.dev.local.

When doing this:
get-Vaultobject -Address https://hashivault.dev.local -Token <token>
It returns this:

uri                   auth_header    
---                   -----------    
http://127.0.0.1:8200 {X-Vault-Token}

First, HUGE thank you for putting this together... I just came across it while working through a tutorial on another site.

At line 1552, you parse the secrets for initializing the vault.

For our org, we wanted to do 7 shares with a threshold of 2.

The script itself does great at actually pushing that, but when it builds the object for the $VaultINITKeys, it makes an assumption that it will have 5 keys.

I did a down-and-dirty cut and paste to expand it for my 7 keys, but a better approach would probably be a foreach loop based on the incoming $initialize variable.

Another possibility, is that the web interface, by default downloads this as a .json file. Possibly just parsing the data a little more "raw" using ConvertFrom-Json would be easier?

I haven't dug in on diagnostics to look at the raw stuff yet, but hopefully this can point this in a direction to make this wonderful toolset a little more generic.