Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Doc]: Description error for - Invoke-AzAksRunCommand -Force #17756

Closed
fredx30 opened this issue Apr 8, 2022 · 1 comment · Fixed by #17761
Closed

[Doc]: Description error for - Invoke-AzAksRunCommand -Force #17756

fredx30 opened this issue Apr 8, 2022 · 1 comment · Fixed by #17761

Comments

@fredx30
Copy link

fredx30 commented Apr 8, 2022

Description

Docs text issue

The -force switch does not appear to have a correct text for the command invoke-azaksruncommand.

Current

The current description text is Remove managed Kubernetes cluster without prompt.

I have run this repetedly with the -force switch and i still have my cluster, im not objecting to the fact i got to keep my cluster but the text is missleading at best. Best i can tell the -force switch only removes the confirmation prompt.

Possible solutions

Investigate what the real functionality is and update description text.

@fredx30 fredx30 added the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Apr 8, 2022
@ghost ghost added the customer-reported label Apr 8, 2022
@fredx30 fredx30 changed the title [Doc]: [Doc]: Descriptions error for - Invoke-AzAksRunCommand -Force Apr 8, 2022
@fredx30 fredx30 changed the title [Doc]: Descriptions error for - Invoke-AzAksRunCommand -Force [Doc]: Description error for - Invoke-AzAksRunCommand -Force Apr 8, 2022
@ghost ghost removed the needs-triage This is a new issue that needs to be triaged to the appropriate team. label Apr 11, 2022
@dingmeng-xue
Copy link
Member

@wyunchi-ms , please check this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants