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

r/log_analytics_workspace: updating the default feature-flag in 3.0 #10885

Closed
tombuildsstuff opened this issue Mar 9, 2021 · 2 comments · Fixed by #15948
Closed

r/log_analytics_workspace: updating the default feature-flag in 3.0 #10885

tombuildsstuff opened this issue Mar 9, 2021 · 2 comments · Fixed by #15948

Comments

@tombuildsstuff
Copy link
Contributor

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

Affected Resource(s)

  • azurerm_log_analytics_workspace

Description

The Feature Flag permanently_delete_on_destroy within the log_analytics_workspace block should be defaulted to true rather than false since the Delete should clean this up automatically, rather than soft-deleting by default - unfortunately this has already shipped, so we'll need to make this breaking change in 3.0.

@github-actions
Copy link

This functionality has been released in v3.0.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

@github-actions
Copy link

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 Apr 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants