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 declaring blob's restorePolicy in azurerm_storage_account #19643

Closed
1 task done
tigonguyen opened this issue Dec 12, 2022 · 1 comment · Fixed by #19644
Closed
1 task done

Support for declaring blob's restorePolicy in azurerm_storage_account #19643

tigonguyen opened this issue Dec 12, 2022 · 1 comment · Fixed by #19644

Comments

@tigonguyen
Copy link

tigonguyen commented Dec 12, 2022

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

Description

Instead of using a new resource block for backup policy on Blob storage. We can add an argument inside blob_properties block when declaring an azurerm_storage_account resource. It's similar the way we work with Microsoft.Storage storageAccounts/blobServices, just declare the restorePolicy argument.

New or Affected Resource(s)/Data Source(s)

Affected to azurerm_storage_account resource

Potential Terraform Configuration

resource "azurerm_storage_account" "main" {
...
  blob_properties {
    restore_policy {
      days = 7
      enabled = true
    }
    delete_retention_policy {
      days = 7
    }
  }
...
}

References

https://learn.microsoft.com/en-us/azure/templates/microsoft.storage/storageaccounts/blobservices?pivots=deployment-language-arm-template

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

Successfully merging a pull request may close this issue.

2 participants