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

Support for permanent delete #7282

Closed
Nilsas opened this issue Jun 10, 2020 · 4 comments
Closed

Support for permanent delete #7282

Nilsas opened this issue Jun 10, 2020 · 4 comments

Comments

@Nilsas
Copy link
Contributor

Nilsas commented Jun 10, 2020

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

Description

Log analytics workspace are now soft-deleted every time you terraform destroy it. For some cases we'd need a reliable way to destroy it and be able to create it with the same name.
Documentation here: https://docs.microsoft.com/en-us/azure/azure-monitor/platform/delete-workspace#permanent-workspace-delete

New or Affected Resource(s)

  • azurerm_log_analytics_workspace

Potential Terraform Configuration

I imagine this being part of the provider features{} block similar to key_vault block.

provider "azurerm" {
  features {
    log_analytics_workspace {
         purge_soft_delete_on_destroy = true
    }
  }
}
@brandonh-msft

This comment has been minimized.

@mathieubrd
Copy link

Any update on this?

The workaround we found is to use a random_integer for the log analytics workspace.

@ahmddp
Copy link

ahmddp commented Jan 13, 2021

Hi, any update on this issue?

@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 Aug 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants