-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
azurerm_monitor_diagnostic_setting - mark retention_policy & retention_policy as optional #6603
Conversation
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.
Hi @nyuen, thanks for this PR!
overall looks good but could we update the website? thanks!
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.
Hey @nyuen, i hope you don't mind by i've pushed the required changes 🙂 LGTM 👍
thanks @katbyte, looks like the linter failed, I guess len(policiesRaw) != 0 should be sufficient. |
heh thats why we have linters 🙂 - and sadly the api can returninconsistentt results depending on many things including region and timing. pushed a commit which should fix that up |
This has been released in version 2.8.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 2.8.0"
}
# ... other configuration ... |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
modifying the Diagnostic settings schema to set the retention policy to Optional #5673
Some resources such as ActivityLogs do not support Retention Policy causing a change on subsequent Terraform apply even if the diagnostic setting. This is caused by a mismatch between the TFState and the object returned by the REST API