-Level Parameter Is Not Always Available When Using -SecurePersonalAccessToken Parameter with Set-VSTeamAccount
bmkaiser opened this issue · 0 comments
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
Billing : 5.1-preview.1
Build : 5.1
Core : 5.1
DistributedTask : 6.0-preview
DistributedTaskReleased : 5.1
ExtensionsManagement : 6.0-preview
Git : 5.1
Graph : 6.0-preview
HierarchyQuery : 5.1-preview
MemberEntitlementManagement : 6.0-preview
Packaging : 6.0-preview
Pipelines : 5.1-preview
Policy : 5.1
Processes : 6.0-preview
Release : 5.1
ServiceEndpoints : 5.0-preview
TaskGroups : 6.0-preview
Tfvc : 5.1
VariableGroups : 5.1-preview.1
Version : AzD
Wiki : 6.0
WorkItemTracking : 6.0-preview.1Log output of $PSVersionTable
Name Value
---- -----
PSVersion 7.3.11
PSEdition Core
GitCommitId 7.3.11
OS Microsoft Windows 10.0.22631
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0