{Role} Clean up linter exclusion rules#31323
Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
| with self.argument_context('ad user') as c: | ||
| c.ignore('_subscription') | ||
| c.argument('mail_nickname', help='mail alias. Defaults to user principal name') | ||
| c.argument('force_change_password_next_login', arg_type=get_three_state_flag(), help='Require the user to change their password the next time they log in. Only valid when --password is specified') |
There was a problem hiding this comment.
May I ask removing this parameter looks like a breaking change, right? If so, why not indicate it in the PR title?
There was a problem hiding this comment.
Good question! force_change_password_next_login has been renamed to force_change_password_next_sign_in (#22432). force_change_password_next_sign_in is no longer used.
Related command
az roleaz adDescription
Clean up linter exclusion rules.