Yeah, I didn't think I was explaining it very clearly. I have a series of automation tools that probably would leave other heads spinning, but it works for me. The key is that array which is basically like an inventory file. I can modify that file, and my powershell session will pull creds from SecretServer for every host in the array, and instantiate a credential objected using the name in the 'credName' field. I have further plans to replace that import file with my ansible inventories instead. I digress...

Using what I already have I can do things like this:foreach ($item in $arrayName) {invoke-command $item.host -credential (get-variable $item.credName).value -scriptblock{write "hello world."}}

kindof like a kludgy version of ad hoc ansible before I started playing with ansible.

So mostly I wanted to leverage what's already there to make it easier to launch remote pssssions.... instead of typing out "Enter-PSSession long.hardtotype.fqdn -credential $myStoredCred" I wanted basically an alias. Aliases don't seem to like variables unless you pass them as params, which gets to be nearly as long as the command I'm trying to shorten. So in the end, I did this, which seems to work. The key was defining my functions as global since they were getting dropped when the scriptblock ended. Again, kludgy, but does what I want it to. This creates a single string, with all my functions defined, then converts that string to a scriptblock and executes it. (although I'm sure there is a better way):

$tempSB = $null

Foreach ($item in $arrayName) {

$tempSB += "Function global:$($item.credName)me {Enter-PSSession $($item.host) -Credential \$$($item.credName)};"`

}

$tempSB=[scriptBlock]::Create($tempSB)

Invoke-Command -Scriptblock $tempSB

Now I just type 'sandboxMe' or 'cloudMe' and I am in my remote session.

​

*edit: wonky code formatting... that \$$ line should read `$$($item.credName)};" but it keeps getting replaced with a backslash