Update New-AzApplicationInsightsWebTest.md

[darrengiles]

added example of creating a test in a disabled state through powershell

Description

Mandatory Checklist

• Please choose the target release of Azure PowerShell

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • N/A

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD update ChangeLog.md file(s) appropriately
  • For SDK-based development mode, update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
    • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • For autorest-based development mode, include the changelog in the PR description.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd]

️✔️Az.ApplicationInsights

️✔️Build

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

️✔️Help Example Check

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

️✔️Help File Existence Check

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

[AarDavMax]

This build appears to have failed, so I'm closing and reopening the PR to restart the build process.

[AarDavMax]

#assign-reviewer:AaronMaxwell

[vidai-msft]

@darrengiles This is an autorest module. The changes are supposed to happen in the generation branch instead of main. You need to update the files under the Examples folder on that branch. Thanks!

[github-actions]

This PR was labeled "needs-revision" because it has unresolved review comments or CI failures.
Please resolve all open review comments and make sure all CI checks are green. Refer to our guide to troubleshoot common CI failures.

[AarDavMax]

@darrengiles I raised the following ICM. https://portal.microsofticm.com/imp/v3/incidents/incident/482477295/summary

The team responsible has requested changes before merging.

[vidai-msft]

@darrengiles Please kindly note the cut off date of development for this sprint is by EOD next Monday. Let me know if you have any questions regarding this PR.

[darrengiles]

@vidai-msft Hello, I don't quite understand what needs to be done for this PR. You mentioned the changes need to be made in another branch, correct? I'm don't think I know how to access this separate branch. Could you share more instructions please?

[AarDavMax]

@vidai-msft The desired changes are very clear within this PR. Please provide additional information related to your earlier comment. Neither @darrengiles or I have any idea what you're referring to when you said, "This is an autorest module. The changes are supposed to happen in the generation branch instead of main. You need to update the files under the Examples folder on that branch. Thanks!". What is the "generation branch" and where can we find the files under the Examples folder on that branch? Is there a work item we should fill out to have someone who works with "autorest modules" jump through the unique hoops for this content?

[vidai-msft]

I have updated with PR [#24508]

[vidai-msft]

Merged into main branch with #24510. Closing this PR.