-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
Ensuring the metadata's persisted for the AzureRM backend #16015
Ensuring the metadata's persisted for the AzureRM backend #16015
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Can we get a full TF_ACC test run output documented here before merging?
nevermind, Azure ACC tests just need a longer timeout
|
Merging this on behalf of @tombuildsstuff so we can include it in the next release. |
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. |
After looking into this, it appears if we don't request the current Metadata before putting the Blob Contents - the Metadata is lost; which means that all information needed to unlock the blob is lost. This PR ensures we retrieve the metadata (e.g. lock information) before pushing the file to blob storage - and adds a test to ensure that the metadata is set correctly when altering.
Fixes #16012
Running this test without this fix:
after this fix: