Availibility of "AvailableInBranch" parameter for each configuration command

Availibility of "AvailableInBranch" parameter for each configuration command

1 vote

avatar

Hi,
the AvailableInBranch param is great for staging concepts by using git. But it should be available in more commands, e.g. I'm missing it for my authentication.ps1 for adapting the SAML2 config to the different params for production and test.

As an alternitive/addition you could provide a global variable in the configuration context which contains the branch. This would allow something like

if ('PRODUCTION' -eq $PSUGITBRANCH) {
    Set-PSUAuthenticationMethod -Type "Saml2" -EntityId "prod" ......
}
elseif ('INTEGRATION' -eq $PSUGITBRANCH) {
    Set-PSUAuthenticationMethod -Type "Saml2" -EntityId "integration" ......
}


I'd prefer the "AvailableInBranch" param and the visibility of all branches (another FR) in the gui.

-Sascha

All Comments (1)

avatar

@callidus2000 That's a good idea. This feature request can out of a very specific customer need but has been adopted by a lot more folks after we rolled it out. I think we should close the loop and make sure we get it implemented on all the commands. I don't see why we couldn't do that.

Adam Driscoll
PowerShell Expert and Software Architect at Devolutions