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 zone redundancy in azurerm_container_registry #11672

Closed
markhoiland opened this issue May 12, 2021 · 1 comment · Fixed by #11706
Closed

Support for zone redundancy in azurerm_container_registry #11672

markhoiland opened this issue May 12, 2021 · 1 comment · Fixed by #11706

Comments

@markhoiland
Copy link

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

A new ACR feature is available for zone-redundancy that should be added as an argument in the resource. This is available for the primary region and the geo-replication region.

New or Affected Resource(s)

  • azurerm_container_registry

Potential Terraform Configuration

resource "azurerm_container_registry" "acr" {
  name                     = "containerRegistry1"
  resource_group_name      = azurerm_resource_group.rg.name
  location                 = azurerm_resource_group.rg.location
  sku                      = "Premium"
  admin_enabled            = false
  zone_redundant           = true
  georeplication_locations       = ["East US", "West Europe"]
  georeplication_zone_redundant  = true
}

References

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