-
Notifications
You must be signed in to change notification settings - Fork 4k
Update Azure Policy examples to address issue #26902 #27040
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Type | Cmdlet | Example | Line | RuleName | Description | Extent | Remediation |
---|---|---|---|---|---|---|---|
Update-AzPolicyAssignment | 10 | 3 | Is_Alias | Set-AzPolicyAssignment is an alias of 'Update-AzPolicyAssignment'. | Set-AzPolicyAssignment -Id $PolicyAssignment.ResourceId -EnforcementMode Default | Use formal name 'Update-AzPolicyAssignment' of the alias 'Set-AzPolicyAssignment'. | |
Update-AzPolicyAssignment | 10 | 3 | Mismatched_Parameter_Value_Type | Set-AzPolicyAssignment -Id $PolicyAssignment.ResourceId is not an expected parameter value type. | -Id | Use correct parameter value type. Expected Type is string. Now the type is .(Command). | |
Update-AzPolicyExemption | 6 | 2 | Is_Alias | Set-AzPolicyExemption is an alias of 'Update-AzPolicyExemption'. | Set-AzPolicyExemption -Id $PolicyExemption.ResourceId -ClearExpiration -BackwardCompatible | Use formal name 'Update-AzPolicyExemption' of the alias 'Set-AzPolicyExemption'. | |
Update-AzPolicyExemption | 6 | 2 | Mismatched_Parameter_Value_Type | Set-AzPolicyExemption -Id $PolicyExemption.ResourceId is not an expected parameter value type. | -Id | Use correct parameter value type. Expected Type is string. Now the type is .(Command). |
️✔️Help File Existence Check
️✔️PowerShell Core - Windows
Hi @mentat9 , please run |
This PR was labeled "needs-revision" because it has unresolved review comments or CI failures. |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
YanaXu
approved these changes
Jan 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update Azure Policy examples to address issue #26902
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
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.