-
Notifications
You must be signed in to change notification settings - Fork 4k
[Get-AzMetric.md]fix: don't worked example 4 #24653
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
Conversation
fix: don't worked example 4
️✔️Az.Monitor
|
Thank you for your contribution sakkuntyo! We will review the pull request and get back to you soon. |
/azp run azure-powershell - security-tools |
Azure Pipelines successfully started running 1 pipeline(s). |
Sorry, there were also errors in the corrected script. I will specify the corrections later. |
This PR was labeled "needs-revision" because it has unresolved review comments or CI failures. |
Just a friendly reminder: our code freeze deadline is at 6 PM PST on April 22nd. If your code is intended for this release, please ensure it is completed as soon as possible. |
Hi @sakkuntyo , I feel the update is not correct. I'll convert it to draft. If you test it, could you provide your test logs or screenshot amd change it to be ready again? |
/azp run azure-powershell - security-tools |
Azure Pipelines successfully started running 1 pipeline(s). |
Hi @sakkuntyo, could you please run the complete test? I see you update the paramter from an string arry to string, could you also run the |
fix: don't worked example 4
Description
Mandatory Checklist
Please choose the target release of Azure PowerShell
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.md
and reviewed the following information:ChangeLog.md
file(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
.## Upcoming Release
header in the past tense.ChangeLog.md
if no new release is required, such as fixing test case only.