-
Notifications
You must be signed in to change notification settings - Fork 574
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
Bug Report: deploy_diagnostics_for_mg variable does not trigger diagnostics deployment #672
Comments
@lachaves Do you perhaps have an idea why this is not working for me? |
Hi @MarcelHeek The MG diag settings are deployed by the AzAPI provider. Can you confirm this is being used? We do not test this module with Rover and the aztfmod caf supermodule. You should raise an issue on that repo as well. |
Hi @matt-FFFFFF, How can I confirm whether this is being used? I am not that much into TF and merely a consumer. I can (at this point) only see that the azure/azapi module v1.5.0 is being loaded through the enterprise-scale module load in the Azure/caf-terraform-landingzone logic And I will look into raising this issue as well in the Azure/caf-terraform-landingzone repo which calls the enterprise_scale module (as a caf solution add-on) |
Hi @MarcelHeek, looking into it right now. |
closed by #1053 |
Community Note
Versions
terraform: 1.3.9
azure provider: 3.50.0
module: 3.3.0
Description : Deploy diagnostics for MG is not triggered.
Describe the bug
Although bumped up to module version 3.3.0 and AzureRM version 3.50.0 and adding the variable to the enterprise_scale.tfvars the plan show no changes to be made that reflect the enabling of diagnostics on Management Groups
Steps to Reproduce
Up the version of the terraform-azurerm-caf-enterprise-scale module in our workflow (Rover based), see screenshot
The plan output only show 1 outside changes and 1 policy assignments change, thats are both non-related to enabling diagnostics on Management Groups
Screenshots
Additional context
Please advice.....
The text was updated successfully, but these errors were encountered: