-
Notifications
You must be signed in to change notification settings - Fork 4k
[Doc]: https://learn.microsoft.com/en-us/powershell/module/az.compute/invoke-azvmruncommand?view=azps-10.4.1 #22968
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
Comments
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Drewm3, @TravisCragg-MSFT, @nikhilpatel909, @sandeepraichura, @hilaryw29, @GabstaMSFT. |
1 similar comment
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Drewm3, @TravisCragg-MSFT, @nikhilpatel909, @sandeepraichura, @hilaryw29, @GabstaMSFT. |
Hey @supachris28 I'm curious which triage page lead you here? And what did you suppose should be populated? |
@isra-fel, I believe it is reasonable for this issue to be filed in this repo because the webpage in question is populated from the cmdlet help. In this case the help for the parameter CommandId is just "The run command ID.", and I think it is fair to say that this help isn't very helpful. @nikhilpatel909, could you work with the teams to update both the API documentation and the PowerShell help to refer to the API/cmdlet that should be used to get a listing of the valid CommandIds. The current documentation doesn't really describe this well. The example is a bit more helpful, but we should not rely only on the examples to explain the API/cmdlet parameters. Additionally, this one is a bit of an extra challenge since many times an ID is typically thought of as either a number or GUID that would represent a specific instance such as a process ID or VM ID. So the fact that this ID is something like "RunShellScript" deserves a bit more in the parameter explanation to make sure it is clear what is needed in this parameter. |
ack, let me work with the teams to get it updated |
Agree with that and sorry for the misunderstanding. I was trying to understand if it's our issue landing page / triage page that needs to be improved. |
@isra-fel It would have been the link at the bottom of the page as I've used with other documentation, but I can't reproduce it now which is a good thing :) |
Valid list of commandIds are here |
@vivlingaiah @Drewm3 please review the linked PR and see if that change is sufficient. |
Public docs have been updated to display the command ID |
Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you! |
Description
It would be good to know what the options are for the CommandId parameter - can you run regular windows scripts?
Also, the epxerience for reporting issues has got much worse with the triage page, it doesn't auto-populate anything now.
The text was updated successfully, but these errors were encountered: