chore(deps): update cloudposse/github-action-terraform-plan-storage action to v2#94
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
d9accfb to
79aa57d
Compare
ba444d6 to
f5d0c88
Compare
c764fe8 to
f6b86af
Compare
e97e7da to
23604a3
Compare
Changes Found for
|
23604a3 to
93768b6
Compare
93768b6 to
f2f5558
Compare
f2f5558 to
07fa078
Compare
07fa078 to
f3f069e
Compare
This file contains hidden or 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
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.
This PR contains the following updates:
v1→v2Release Notes
cloudposse/github-action-terraform-plan-storage (cloudposse/github-action-terraform-plan-storage)
v2.0.0Compare Source
Google backends: gcs and firestore (#35) @goruha (#36)
what
Use google services to store state (gcs) and metadata (firestore)
why
For those who use google cloud it is hard to adopt atmos as all the GH tooling is built around AWS. This PR and several other fixes that.
references
See also related PRs in:
Usage
To use the GCP implementation, specify planRepositoryType as gcs and metadataRepositoryType as firestore, then provide the following GCP-specific settings: googleProjectId to specify the project for both GCS bucket and Firestore, bucketName for GCS storage, and googleFirestoreDatabaseName/googleFirestoreCollectionName for Firestore metadata.
The component, stack, planPath, and action parameters work the same way as in AWS and Azure examples.
🤖 Automatic Updates
Update .github/settings.yml @osterman (#33)
what
.github/settings.yml.github/auto-release.ymlfileswhy
.github/settings.ymlfrom org levelreferences
v2Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.