Support GCS (Google Cloud Storage) as storage for tfmigrate history files #473
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you for your contribution! |
|
It looks good. |
|
I've confirmed it works well. |
|
Thanks for your review and documentation! |
|
Published the prerelease version https://github.com/suzuki-shunsuke/tfaction/releases/tag/v0.5.16-0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From v0.3.7, tfmigrate now supports GCS as history backend.
I believe that it is possible for tfaction to realize #59, so here I'm going to propose a change to close it.
To be honest, I'm not so sure how I should test tfaction.
I've confirmed that the added GitHub action can print expected outputs, but please tell me if it is not enough to keep this new feature tested well. 🙇