v0.1.18

Overview

• Introduce syncing diagram to state backend (currently supported backends are S3, GCS and Azure Blob Storage)
  • Add sync-to-backend flag to the end of any pluralith run command to store a copy of the diagram alongside your Terraform state
• Improve experimental terragrunt support

Changelog

• 44fb742 Merge pull request #71 from Pluralith/feature-diagram-in-tf-backend
• 80f4fc7 Merge pull request #72 from Pluralith/dev
• de4df10 chore: Adapt backend naming
• 5faa79f chore: Commit progress on auto-update mechanism
• d7e0538 chore: Commit progress with storing diagram in Azure backend
• b3e54cd chore: Update version
• fe3d0bd feat: Add flag for syncing diagram to backend
• 9068545 feat: Add support for storing diagram at multi-level state key
• 291df86 feat: Check if remote backend exists and handle if not
• 1b49790 feat: Commit progress with storing diagram in Azure backend
• f385658 feat: Handle loading backend config from state for three big providers
• d30b052 feat: Handle unsupported backends
• 1a025b6 feat: Implement storing diagram in Azure backend
• 2638ae1 feat: Implement storing diagram in S3 backend
• 1a32d8e feat: Implement storing diagram in gcs backend
• ae51ab2 feat: Improve splitting json plan
• 26a2c41 feat: Introduce passing existing plan files to run commands
• 1bdbdbd feat: Make terraform init check conditional on plan file presence
• c93072e feat: Rework apply UX to show terraform outputs
• 11c4f9f fix: Add returns on error in run command entry files
• 43cb49b fix: Adjust spinner message
• 63a267d fix: Resolve issue with error message on successful backend sync
• b54f669 fix: Resolve issue with terraform init skip on plan-file-json pass