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

v2.0.0

What's Changed

This release introduces the concept of "hooks" in pipelines-root.yml as a mechanism to customize the account factory workflows. The intention is that consumers will fork pipelines-workflows, add a step to checkout their own actions repository (or their own fork of pipelines-actions), and then change the "uses" block in the pre/post steps to point to their customized workflows.

We're actively trying to balance providing a highly extensible mechanism for users to adapt pipelines to their needs, whilst also maintaining upgrade-ability down the line. We hope that by encouraging customizations to live in separate actions that future updates to pipelines-root.yml will not cause significant merge conflicts, and that updates to pipelines-actions can continue to be pulled in via a version bump, even in a highly customized environment.

🛠️ Breaking Changes

This release includes a breaking change requiring that a minimum version of v0.59.5 for Terragrunt is used in CI.

This is due to the fact that Pipelines now integrates with the newly available dynamic authentication capabilities in Terragrunt.

For most, this entails making an update to the .mise.toml file in the root of the repository where Pipelines runs.

While this is the minimum version required, take note of the bug fix introduced in v0.59.7. If you are using the get_aws_account_id function in your Terragrunt configurations, you are advised to upgrade to this version to incorporate that bug fix.

New Action Usage

For Pipelines users that allowlist specific actions, version 2.0 includes the following new actions

• ./pipelines-actions/.github/custom-actions/pre-provision-new-account
• ./pipelines-actions/.github/custom-actions/post-provision-new-account
• ./pipelines-actions/.github/custom-actions/pre-baseline-core-accounts
• ./pipelines-actions/.github/custom-actions/post-baseline-core-accounts
• ./pipelines-actions/.github/custom-actions/pre-baseline-child-account
• ./pipelines-actions/.github/custom-actions/post-baseline-child-account
• ./pipelines-actions/.github/custom-actions/post-create-delegated-repo

Changelog

• Use pipelines auth for terragrunt execute by @Resonance1584 in #37
• chore: add bootstrap to root, make bootstrap step id consistent by @ZachGoldberg in #41
• Fix missed rename by @Resonance1584 in #42
• Customization Hooks by @ZachGoldberg in #40
• fix: Moving yml configurations for custom actions to an action.yml nested under the action name by @yhakbar in #43

Full Changelog: v1...v2.0.0

v1.5.0

What's Changed

• Remove out of date comment by @Resonance1584 in #35
• chore: Bump pipelines-actions to v1.3.3 by @yhakbar in #36

Breaking Changes

As of this release, the gruntwork-installer-version and boilerplate-version versions are no longer configurable in the .gruntwork/config.yml in infrastructure-live repositories.

They are now configurable as environment variables directly in the workflows instead, as the average customer has no need to configure them on a per-infrastructure-live repository basis.

No action needs to be taken to adopt this change. Just take note that the configurations in .gruntwork/config.yml will be ignored if present.

Full Changelog: v1...v1.5.0

v1

Merge pull request #36 from gruntwork-io/chore/bump-pipelines-actions

chore: Bump `pipelines-actions` to `v1.3.3`

v1.4.0

What's Changed

• Add runner as input by @Resonance1584 in #34
• chore: Bump pipelines-actions to 1.3.2 by @yhakbar in #33
• feat: Migrating unnecessary configs out of .gruntwork/config.yml by @yhakbar in #32

Full Changelog: v1...v1.4.0

v1.3.2

What's Changed

• Bump pipelines to 0.10.1 actions to 1.3.1 by @Resonance1584 in #31

Full Changelog: v1...v1.3.2

v1.3.1

What's Changed

• Upgrade pipelines-cli and actions to use tfplan output by @Resonance1584 in #30

Full Changelog: v1...v1.3.1