v2.6.0

New Features

• We now allow for specifying arbitrary env values via config.yml. See the docs for an example of how to set .pipelines.env with your custom environment values.
• An update to the pipelines-unlock workflow with an optional unlock_all flag that iterates over every state file and unlocks all of them. This is useful in the event of a large run, e.g. run-all plan that is cancelled midway leaving many locks stuck.

Enhancements

• Pipelines now detects if the PIPELINES_READ_TOKEN is invalid and posts a more helpful error to logs, the PR comment and the step summary letting you know to ensure the token is valid.

PR Changelog

• Pipelines CLI v0.23.0 by @Resonance1584 in #71
• Pipelines CLI v0.23.1 by @Resonance1584 in #72
• Pipelines CLI v0.24.0 by @Resonance1584 in #74
• Force unlock all by @ZachGoldberg in #77
• feat: detect invalid read tokens by @ZachGoldberg in #80
• chore: Bumping pipelines-cli to v0.28.0 by @yhakbar in #81

Full Changelog: v2...v2.6.0

v2

This is a floating release tracking the latest release with major version 2.

v2.5.0

What's Changed

• DEV-427 - Unlock State Workflow by @ZachGoldberg in #64
• chore: Bumping pipelines to v0.21.2 by @yhakbar in #65
• DEV-129: Add additional pipelines preflight checks by @ZachGoldberg in #67
• Fix action reference in account bootstrap job's name by @oredavids in #70
• Bump to version v1.9.0 of pipelines-actions which brings in complementary changes for the above new features (unlocking and preflight) as well as a handful of bug fixes - https://github.com/gruntwork-io/pipelines-actions/releases/tag/v1.9.0

Full Changelog: v2...v2.5.0

v2.4.0

What's Changed

This pulls in a change to Pipelines HCL Configuration as Code system to segment the aws_accounts block into an accounts block nested as the aws block.

While this is a breaking change, it is not in use by any customers at the moment, and should be safe to use without modification.

Changelog

• chore: Bumping pipelines and pipelines-actions versions by @yhakbar in #63

Full Changelog: v2.3.3...v2.4.0

v2.3.3

What's Changed

This pulls in a rename of the pipelines HCL configuration block for Pipelines to repository via updates to the pipelines-cli.

In addition, it pulls in changes to pipelines-actions which result in a new CATALOG_TAGS value being used during repository vending. This allows for central management of AWS cost allocation tags for delegated repositories.

Some plumbing changes have been done in addition to improve the configurability of the TF_BINARY configuration, making it easier to decide whether you want to use OpenTofu or Terraform.

Changelog

• feat: Bumping pipelines-cli to v0.20.0 and pipelines-actions to v1.8.0 by @yhakbar in #62

Full Changelog: v2...v2.3.3

v2.3.2

• Include bugfix version of pipelines actions https://github.com/gruntwork-io/pipelines-actions/releases/tag/v1.7.1

Full Changelog: v2...v2.3.2

v2.3.1

What's Changed

• chore: Bumping pipelines-cli to v0.19.1 by @yhakbar in #61

Full Changelog: v2.3.0...v2.3.1

v2.3.0

What's Changed

• feat: Adding pipelines.yml workflow by @yhakbar in #51
• chore: Bumping pipelines-cli to v0.19.0 by @yhakbar in #60
• chore: Bumping pipelines-actions to v1.7.0 by @yhakbar in #59

Full Changelog: v2.2.1...v2.3.0

v2.2.1

What's Changed

• Bump to version v1.5.0 of pipelines actions which includes an updated commenting strategy that should be much faster for all users.
• Fix delegated workflow's bootstrap reference by @oredavids in #48

New Contributors

• @oredavids made their first contribution in #48

Full Changelog: v2...v2.2.0

v2.1.0

What's Changed

Take special note of the changes in #45. It introduces significant changes to how Pipelines workflows operate, and should be evaluated carefully when considering an upgrade to this release.

In particular, #45 changes the behavior of the EnvCommonChanged job. Pipelines Orchestrate will no longer emit a single job for each AWS account, looking for relevant updates to an _envcommon file that has changed. Instead, a single job will be emitted from the root of the repository that will look for changes throughout the repository. This change leverages the new capabilities released as of v2.0.0 where Terragrunt will dynamically assume the correct role in a given directory through integration with Pipelines.

Changelog

• fix: Adjusting delegated workflow so that it uses dynamic authentication too by @yhakbar in #44
• feat: Bumping Pipelines CLI to v0.15.1 by @yhakbar in #45
• chore: Pin actions version by @yhakbar in #46

Full Changelog: v1.6.0...v2.1.0