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

allow_blob_public_access causes storage account deployment to break in government environment #7812

Closed
Stosija opened this issue Jul 20, 2020 · 5 comments · Fixed by #8092
Closed
Labels
azure/government bug documentation service/storage upstream/microsoft Indicates that there's an upstream issue blocking this issue/PR
Milestone

Comments

@Stosija
Copy link

Stosija commented Jul 20, 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

Last week I tried deploying several storage accounts to a resource group in a US Government environment. The deployments threw an error saying that the feature was not available in that region. I replicated the behavior today. I discovered that change #7739 was made last Tuesday, which was also the last day I successfully deployed a storage account via Terraform. I changed the provider version back to 2.18 and was able to deploy a storage account.

Affected Resource(s)

*azurerm_storage_account

Terraform Configuration Files

provider "azurerm" {
  environment = "usgovernment"
  version =  ">= 2.13.0"
  features {}
}

resource "azurerm_storage_account" "example" {
  name = "storageaccountname"
  resource_group_name = azurerm_resource_group.example.name
  location = "usgovvirginia"
  account_tier = "Standard"
  account_replication_type = "LRS"
  allow_blob_public_access = false
}

Debug Output

Failure sending request: StatusCode=400 -- Original Error: Code="FeatureNotAvailableInRegion" Message="allowBlobPublicAccess feature is not available in this region"

Expected Behavior

Expected the storage account to successfully deploy.

Actual Behavior

The storage account failed to deploy.

Steps to Reproduce

  1. terraform apply

Important Factoids

This behavior is happening in a US Gov environment.

References

@lrxtom2

This comment has been minimized.

@vsabella

This comment has been minimized.

@lstroud

This comment has been minimized.

@WodansSon WodansSon added upstream/microsoft Indicates that there's an upstream issue blocking this issue/PR documentation labels Aug 11, 2020
WodansSon added a commit that referenced this issue Aug 13, 2020
* - filter  and  from Azure US Government

* Update code

* Update code

* Revert changes to client and update env checks

* Update test cases

* Revert gov env test case

* Fix set logic

Co-authored-by: Jeffrey Cline <[email protected]>
@WodansSon WodansSon added this to the v2.23.0 milestone Aug 13, 2020
@ghost
Copy link

ghost commented Aug 13, 2020

This has been released in version 2.23.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.23.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Sep 12, 2020

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!

@ghost ghost locked and limited conversation to collaborators Sep 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.