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

storage: caching the Resource Group Name / Account Key #4205

Merged
merged 5 commits into from Sep 2, 2019

Conversation

tombuildsstuff
Copy link
Member

This PR introduces caching for both the Resource Group Name and the Account Key for a Storage Account. Due to the way this works the test check functions had to be updated to confirm we get an error (404) rather than the resource group name being not found

@ghost ghost added the size/M label Sep 1, 2019
@tombuildsstuff tombuildsstuff added this to the v1.34.0 milestone Sep 1, 2019
@tombuildsstuff
Copy link
Member Author

Ignoring a couple of known test failures, which will be fixed via #4179 and another PR (tomorrow) the tests pass:

Screenshot 2019-09-01 at 11 38 20

Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@tombuildsstuff
Copy link
Member Author

The Travis failure is because a dependency is offline - but the tests pass:

Screenshot 2019-09-02 at 10 48 39

@tombuildsstuff tombuildsstuff merged commit 27e7206 into master Sep 2, 2019
@tombuildsstuff tombuildsstuff deleted the f/storage-account-key-caching branch September 2, 2019 08:49
tombuildsstuff added a commit that referenced this pull request Sep 2, 2019
@ghost
Copy link

ghost commented Sep 18, 2019

This has been released in version 1.34.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 = "~> 1.34.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Oct 2, 2019

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 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Oct 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants