Skip to content

chore(deps): update cloudposse/github-action-terraform-plan-storage action to v2#94

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/cloudposse-github-action-terraform-plan-storage-2.x
Open

chore(deps): update cloudposse/github-action-terraform-plan-storage action to v2#94
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/cloudposse-github-action-terraform-plan-storage-2.x

Conversation

@renovate

@renovate renovate Bot commented Dec 3, 2024

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
cloudposse/github-action-terraform-plan-storage action major v1v2

Release Notes

cloudposse/github-action-terraform-plan-storage (cloudposse/github-action-terraform-plan-storage)

v2.0.0

Compare 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.

 - name: Store Plan
    uses: cloudposse/github-action-terraform-plan-storage@v2
    id: store-plan
    with:
      action: storePlan
      planPath: my-plan.tfplan
      component: mycomponent
      stack: core-mycomponent-use1
      planRepositoryType: gcs
      metadataRepositoryType: firestore
      bucketName: my-terraform-plans
      gcpProjectId: my-gcp-project
      gcpFirestoreDatabaseName: terraform-plan-metadata
      gcpFirestoreCollectionName: terraform-plan-storage

 - name: Get Plan
    uses: cloudposse/github-action-terraform-plan-storage@v2
    id: get-plan
    with:
      action: getPlan
      planPath: my-plan.tfplan
      component: mycomponent
      stack: core-mycomponent-use1
      planRepositoryType: gcs
      metadataRepositoryType: firestore
      bucketName: my-terraform-plans
      gcpProjectId: my-gcp-project
      gcpFirestoreDatabaseName: terraform-plan-metadata
      gcpFirestoreCollectionName: terraform-plan-storage
🤖 Automatic Updates
Update .github/settings.yml @​osterman (#​33)
what
  • Update .github/settings.yml
  • Drop .github/auto-release.yml files
why
  • Re-apply .github/settings.yml from org level
  • Use organization level auto-release settings
references
  • DEV-1242 Add protected tags with Repository Rulesets on GitHub

v2

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot requested review from a team as code owners December 3, 2024 20:43
@renovate renovate Bot force-pushed the renovate/cloudposse-github-action-terraform-plan-storage-2.x branch from d9accfb to 79aa57d Compare May 13, 2025 11:31
@renovate renovate Bot force-pushed the renovate/cloudposse-github-action-terraform-plan-storage-2.x branch 2 times, most recently from ba444d6 to f5d0c88 Compare July 28, 2025 19:30
@renovate renovate Bot force-pushed the renovate/cloudposse-github-action-terraform-plan-storage-2.x branch 3 times, most recently from c764fe8 to f6b86af Compare October 1, 2025 05:55
@renovate renovate Bot force-pushed the renovate/cloudposse-github-action-terraform-plan-storage-2.x branch 2 times, most recently from e97e7da to 23604a3 Compare October 3, 2025 20:39
@github-actions

github-actions Bot commented Oct 3, 2025

Copy link
Copy Markdown

Changes Found for foobar/changes in plat-ue2-sandbox


create

Plan: 1 to add, 0 to change, 0 to destroy.
To reproduce this locally, run:

atmos terraform plan foobar/changes -s plat-ue2-sandbox

Create

+ random_id.foo[0]
Terraform Plan Summary
  # random_id.foo[0] will be created
  + resource "random_id" "foo" {
      + b64_std     = (known after apply)
      + b64_url     = (known after apply)
      + byte_length = 8
      + dec         = (known after apply)
      + hex         = (known after apply)
      + id          = (known after apply)
      + keepers     = {
          + "seed" = "foo-plat-ue2-sandbox-blue"
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Warning: Test warning summary

  with data.validation_warning.warn[0],
  on main.tf line 20, in data "validation_warning" "warn":
  20: data "validation_warning" "warn" {

Test warning details

Warning

Warning: Test warning summary

  with data.validation_warning.warn[0],
  on main.tf line 20, in data "validation_warning" "warn":
  20: data "validation_warning" "warn" {

Test warning details

@renovate renovate Bot force-pushed the renovate/cloudposse-github-action-terraform-plan-storage-2.x branch from 23604a3 to 93768b6 Compare November 10, 2025 22:45
@renovate renovate Bot force-pushed the renovate/cloudposse-github-action-terraform-plan-storage-2.x branch from 93768b6 to f2f5558 Compare December 15, 2025 15:31
@renovate renovate Bot force-pushed the renovate/cloudposse-github-action-terraform-plan-storage-2.x branch from f2f5558 to 07fa078 Compare December 31, 2025 18:05
@renovate renovate Bot force-pushed the renovate/cloudposse-github-action-terraform-plan-storage-2.x branch from 07fa078 to f3f069e Compare February 2, 2026 16:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants