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

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/github-action-terraform-plan-storage	action	major	v1 → v2

---

Release Notes

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

v2.0.1

Compare Source

Deprecate in favor of Atmos Native CI @​osterman (#​39)

what

Marks this action as deprecated in README.yaml and the regenerated README.md, with the warning above Introduction in place of the Atmos tip.

Repair CODEOWNERS validation using GitHub's repository API, retaining syntax and duplicate-pattern checks without requiring the unavailable personal access token.

why

This action's functionality has moved into the Atmos CLI itself (Native CI). The atmos binary already warns at runtime when it detects invocation from this action; this PR adds the equivalent static warning to the README so it's visible before the action is even added to a workflow.

references

• https://atmos.tools/deprecated/github-actions/terraform-plan-storage
• https://atmos.tools/ci
• Depends on cloudposse/.github#283; merge the shared-template change first so future README generation preserves this placement.

🤖 Automatic Updates

Replace Makefile with atmos.yaml @​osterman (#​37)

what

• Remove Makefile
• Add atmos.yaml

why

• Replace build-harness with atmos for readme genration

References

• DEV-3229 Migrate from build-harness to atmos

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:

• cloudposse/github-action-atmos-terraform-plan#93
• cloudposse/github-action-atmos-terraform-apply#64
• cloudposse/github-action-atmos-affected-stacks#55

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

---

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.