When using Set-VSTeamAccount with tab completion for parameters, the -Level parameter does not auto-complete if it's not declared before the -SecurePersonalAccessToken parameter. You can still successfully execute the command regardless of order, but it seems like the -Level parameter is not part of the Secure parameter set.
Scenario 1 - Tab Completion Works as Expected
Set-VSTeamAccount -Level User -SecurePersonalAccessToken $spat -Account abc -Version AzD
Scenario 2 - Tab Completion Does Not Work as Expected
Set-VSTeamAccount -SecurePersonalAccessToken $spat -Account abc -Version AzD -Level User
Expected behavior
Tab completion works for the -Level parameter regardless of parameter order or parameter set for all Windows devices.
Actual behavior?
When using Set-VSTeamAccount with the -SecurePersonalAccessToken parameter, the -Level parameter does not auto-complete if declared after -SecurePersonalAccessToken.
Steps to reproduce
When using
Set-VSTeamAccount
with tab completion for parameters, the-Level
parameter does not auto-complete if it's not declared before the-SecurePersonalAccessToken
parameter. You can still successfully execute the command regardless of order, but it seems like the-Level
parameter is not part of the Secure parameter set.Scenario 1 - Tab Completion Works as Expected
Set-VSTeamAccount -Level User -SecurePersonalAccessToken $spat -Account abc -Version AzD
Scenario 2 - Tab Completion Does Not Work as Expected
Set-VSTeamAccount -SecurePersonalAccessToken $spat -Account abc -Version AzD -Level User
Expected behavior
Tab completion works for the
-Level
parameter regardless of parameter order or parameter set for all Windows devices.Actual behavior?
When using
Set-VSTeamAccount
with the-SecurePersonalAccessToken
parameter, the-Level
parameter does not auto-complete if declared after-SecurePersonalAccessToken
.On Which OS have you tried it?
Windows
What was your server version?
Azure DevOps Services
Other server version
No response
Log output of used API
Log output of $PSVersionTable