Skip to content
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

Retention policy days are ignored inside "enabled_log" for azurerm_monitor_diagnostic_setting" module #23025

Closed
1 task done
adrigomez85 opened this issue Aug 21, 2023 · 2 comments · Fixed by #23029
Closed
1 task done

Comments

@adrigomez85
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Terraform Version

3.70.0

AzureRM Provider Version

3.70.0

Affected Resource(s)/Data Source(s)

azurerm_monitor_diagnostic_setting

Terraform Configuration Files

resource "azurerm_monitor_diagnostic_setting" "agw" {
  name               = "${var.deployment_def.code}-logaw-appgw-diag"
  target_resource_id = azurerm_application_gateway.local.id
  storage_account_id = data.azurerm_storage_account.agw.id
  enabled_log {

    category_group = "allLogs"

    retention_policy {
      enabled = true
      days    = 60
    }
  }

  metric {

    category = "Allmetrics"

    retention_policy {
      enabled = true
      days    = 50
    }
  }

}

Debug Output/Panic Output

No changes. Your infrastructure matches the configuration.

Expected Behaviour

When "days" value is being updated it has to be detected by Terraform and updated in Azure.

Actual Behaviour

Change is not being detected by Terraform.

Steps to Reproduce

No response

Important Factoids

No response

References

No response

@HappyTobi
Copy link
Contributor

Copy link

github-actions bot commented May 7, 2024

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants