-
Notifications
You must be signed in to change notification settings - Fork 454
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
[PSRule] Fix Rule Azure.VM.AMA #3938
Conversation
@@ -567,19 +567,21 @@ resource vm_logAnalyticsWorkspace 'Microsoft.OperationalInsights/workspaces@2021 | |||
scope: az.resourceGroup(split(monitoringWorkspaceId, '/')[2], split(monitoringWorkspaceId, '/')[4]) | |||
} | |||
|
|||
module vm_microsoftMonitoringAgentExtension 'extension/main.bicep' = if (extensionMonitoringAgentConfig.enabled) { | |||
name: '${uniqueString(deployment().name, location)}-VM-MicrosoftMonitoringAgent' | |||
module vm_azureMonitorAgentExtension 'extension/main.bicep' = if (extensionMonitoringAgentConfig.enabled) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per similar discussion for VMSS (ref #3918 (comment)) we won't be including this change into release 0.11 to avoid an additional breaking change. We should discuss and decide on if keeping both AMA and MMA extensions or if discontinuing support for MMA
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as for the other, I believe this can and should be merged
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ping @eriqua :D By now already have quite some conflicts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Plus I believe @rahalan is already working on the migration into AVM. So it's high time this is merged.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ping @eriqua
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looping in @rahalan, AVM VM and VMSS module owner, to finalize the decision on if keeping the legacy MMA support or just remove it as part of migration to AVM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Has to be merged into AVM module as soon as its PR is merged
Closing PR as merged in via PR Azure/bicep-registry-modules#717 and expanded on in PR Azure/bicep-registry-modules#784. Thanks @fabmas :) |
Pull request was closed
## Description - Retored the functionality introduced by PR Azure/ResourceModules#3938 - Updated Set-AVMModule utility to be able to handle modules that don't use plane test names like `max` but instead e.g., `<prefix>.max` - Small update to docs and regeneration of files - Shifted deployment location as encountering capacity issues in WestEurope - Added a warning supression for Network/Connection that was added for the same reason | Pipeline | | - | | [![avm.res.compute.virtual-machine](https://github.com/AlexanderSehr/bicep-registry-modules/actions/workflows/avm.res.compute.virtual-machine.yml/badge.svg?branch=users%2Falsehr%2FvmUpdate20240110&event=workflow_dispatch)](https://github.com/AlexanderSehr/bicep-registry-modules/actions/workflows/avm.res.compute.virtual-machine.yml) | --------- Co-authored-by: Erika Gressi <[email protected]>
Description
Fix Rule Azure.VM.AMA
Close Azure/bicep-registry-modules#2377
Pipeline references
Type of Change
Checklist