Gruntwork release 2024-07

Guides / Update Guides / Releases / 2024-07

This page is lists all the updates to the Gruntwork Infrastructure as Code Library that were released in 2024-07. For instructions on how to use these updates in your code, check out the updating documentation.

Here are the repos that were updated:

patcher-cli
pipelines-actions
pipelines-cli
pipelines-workflows
terraform-aws-architecture-catalog
terraform-aws-cis-service-catalog
terraform-aws-control-tower
terraform-aws-data-storage
terraform-aws-ecs
terraform-aws-eks
terraform-aws-monitoring
terraform-aws-service-catalog
terrapatch-cli

patcher-cli

v0.9.0

Published: 7/2/2024 | Release notes

This is the next major release of Patcher, which has features designed to support the next version of our promotion workflows.

⭐ Patcher now supports publishing the results of an upgrade as a GitHub Pull Request. ⭐

The update command now supports three additional flags:

--publish: Publish the changes to the remote Git repository and open a pull request.
--pr-branch: The branch to create.
--pr-title: The pull request's title.

You can publish the result of an upgrade like this:

patcher update --non-interactive --update-strategy next-breaking --publish --pr-title &quot;Update Dependencies&quot; --pr-branch &quot;patcher-update-deps&quot;

Patcher will perform the upgrade as usual, check out a new Git branch, commit the changes, push them to GitHub, and open a pull request.

The following environment variables must be configured when using the --publish flag:

GIT_AUTHOR_NAME: The Git Author Name. e.g: Patcher CI.
GIT_AUTHOR_EMAIL: The Git Author Email. e.g: patcher@gruntwork.io.

Note: You can only use the publish features when using the update command in non-interactive mode.

Patcher now supports Upgrade Plan and Spec files, which make upgrades more deterministic. Previously, a new dependency version could be released while Patcher was upgrading separate accounts (e.g., ' devandstage`). Patcher would correctly promote the change to the next environment, e.g., dev -> stage, but it didn't guarantee the exact version was used.

Here is an overview of each type.

An upgrade plan contains detailed information on all discovered dependencies, their current versions, and available updates. It also contains information about matched files and patterns used for discovery. When you use an upgrade plan with the update command, Patcher will skip resolving dependencies and use the metadata encoded in the plan. You can write an upgrade plan to a file by using the report command with the --output-flag flag:

patcher report --output-plan plan.json
cat plan.json | jq &quot;.&quot;

Note: We’ve omitted the contents for brevity.

While an upgrade plan comprehensively represents the current state and all possible updates, an upgrade spec is a simplified, target-orientated representation of the desired end state after an upgrade. It is used to promote consistent upgrades across different environments, even if dependency usages are located in different files.

Here’s the contents of an example spec file:

&#x7B;
  &quot;IncludeDirPattern&quot;: &quot;&#x7B;*dev*&#x7D;/**&quot;,
  &quot;ExcludeDirPattern&quot;: &quot;&quot;,
  &quot;Dependencies&quot;: [
    &#x7B;
      &quot;ID&quot;: &quot;gruntwork-io/terraform-aws-cis-service-catalog/landingzone/account-baseline-app&quot;,
      &quot;Org&quot;: &quot;gruntwork-io&quot;,
      &quot;Repo&quot;: &quot;terraform-aws-cis-service-catalog&quot;,
      &quot;Module&quot;: &quot;landingzone/account-baseline-app&quot;,
      &quot;Constraints&quot;: null,
      &quot;TargetSafeVersion&quot;: null,
      &quot;TargetBreakingVersion&quot;: &quot;0.41.0&quot;
    &#x7D;,
    &#x7B;
      &quot;ID&quot;: &quot;gruntwork-io/terraform-aws-cis-service-catalog/networking/vpc&quot;,
      &quot;Org&quot;: &quot;gruntwork-io&quot;,
      &quot;Repo&quot;: &quot;terraform-aws-cis-service-catalog&quot;,
      &quot;Module&quot;: &quot;networking/vpc&quot;,
      &quot;Constraints&quot;: null,
      &quot;TargetSafeVersion&quot;: null,
      &quot;TargetBreakingVersion&quot;: &quot;0.41.0&quot;
    &#x7D;
  ]
&#x7D;

The report command has been changed to now show the upgrade spec by default.

The report command can now include or exclude directories used for discovery using double-star glob patterns. This feature can generate a report of outdated dependencies for select accounts. For example you might have a number of "dev" accounts in your infrastructure-live directory e.g: team-alpha-dev-account and team-beta-dev-account. Use the discovery filters to generate a report with dev accounts only:

patcher report --include-dirs &quot;*-dev-*/**&quot; test/fixtures/report/infrastructure-live-cis-large | jq &quot;.&quot;

Or generate a report on standalone accounts only. e.g: logs, security, and shared:

patcher report --exclude-dirs &quot;&#x7B;_*,*-dev-*,*-stage-*,*-prod-*&#x7D;/**&quot; | jq &quot;.&quot;

Previously, the apply command was the only command that supported a dry-run mode when testing patches. Patcher can now simulate all operations when running the update command in non-interactive mode, which makes it especially useful for validating CI test workflows.

You can invoke the dry run mode by specifying the --dry-run flag:

patcher update --non-interactive --update-strategy next-breaking --dry-run

Add the ability to include or exclude report command dependencies.
Add support for outputting plan and spec files.
Add support for publishing pull requests using the update command.
Add support for a global dry-run mode to simulate operations.
Change the report command to output upgrade specifications.
Bump upstream dependencies.

Full Changelog: https://github.com/gruntwork-io/patcher-cli/compare/v0.8.4...v0.9.0

pipelines-actions

v1.9.0

Published: 7/26/2024 | Release notes

fix: read tf versions from config by @gruntwork-ci in https://github.com/gruntwork-io/pipelines-actions/pull/50
fix: shell default expansion by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-actions/pull/53
feat: pass through new params for customizing delegated repos by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-actions/pull/52
Chore: more flexible mise config read regex by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-actions/pull/51
DEV-427 - Support for force unlock workflow by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-actions/pull/54
Add comment when infrastructures changes are not detected by @oredavids in https://github.com/gruntwork-io/pipelines-actions/pull/56
DEV-159: Fix idempotency in creating access control PRs by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-actions/pull/59
Dev-441 fix empty bootstrap by @odgrim in https://github.com/gruntwork-io/pipelines-actions/pull/58
Add extra logging if SKIP_TERRAGRUNT is set by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-actions/pull/60
DEV-129: Add additional pipelines preflight checks by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-actions/pull/57
@odgrim made their first contribution in https://github.com/gruntwork-io/pipelines-actions/pull/58

Full Changelog: https://github.com/gruntwork-io/pipelines-actions/compare/v1.8.0...v1.9.0

v1.8.0

Published: 7/16/2024 | Release notes

New catalog tags value passthrough for account factory by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-actions/pull/48
feat: Using updated pipelines config repository instead of pipelines config pipelines by @yhakbar in https://github.com/gruntwork-io/pipelines-actions/pull/49

Full Changelog: https://github.com/gruntwork-io/pipelines-actions/compare/v1.7.1...v1.8.0

v1.7.1

Published: 7/16/2024 | Release notes

Bugfix - Default arch_catalog_repo_url had a typo.

Full Changelog: https://github.com/gruntwork-io/pipelines-actions/compare/v1.7.0...v1.7.1

v1.7.0

Published: 7/15/2024 | Release notes

Fixes for provisioning delegated repositories.
Removal of unnecessary Plan Summary section on comments for applies.

Full Changelog: https://github.com/gruntwork-io/pipelines-actions/compare/v1.6.1...v1.7.0

v1.6.1

Published: 7/10/2024 | Release notes

New flag to disable provisioning accounts by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-actions/pull/40
Use github event name to determine pipelines event type by @oredavids in https://github.com/gruntwork-io/pipelines-actions/pull/38
fix: Hide . working directory by @yhakbar in https://github.com/gruntwork-io/pipelines-actions/pull/42

Full Changelog: https://github.com/gruntwork-io/pipelines-actions/compare/v1.6.0...v1.6.1

v1.6.0

Published: 7/9/2024 | Release notes

Update bootstrap action to use binary for deploy branch config by @oredavids in https://github.com/gruntwork-io/pipelines-actions/pull/36
DEV-376: Pass through VPC inputs for baseline customization by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-actions/pull/41
fix: Adding default for tf_binary by @yhakbar in https://github.com/gruntwork-io/pipelines-actions/pull/39

Full Changelog: https://github.com/gruntwork-io/pipelines-actions/compare/v1.5.0...v1.6.0

v1.5.0

Published: 7/8/2024 | Release notes

This version of pipelines-actions introduces a new architecture for how we manage state for updating comments with the results of plans/applies. The prior architecture included a central mutex to "lock" a state file to ensure that state was consistent across multiple parallel-jobs. The issue with the mutex is locking and unlocking was slow, and with many jobs in parallel (20+) could introduce severe delays to overall pipelines runs. The updated architecture uploads a distinct artifact per job, which then gets aggregated when updating the comment. This removes the need for any central locking and results in a ~20s speedup for small pipelines runs, and a dramatic speedup for large jobs.

Remove the Mutex around posting comments, replace with alternative synchronization strategy by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-actions/pull/24
fix: dev-364: use deploy branch name everywhere by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-actions/pull/34
Fix: Don't break if we don't have a valid merged pr url by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-actions/pull/35
fix: Set default deploy branch name to main when not defined by @yhakbar in https://github.com/gruntwork-io/pipelines-actions/pull/37

Full Changelog: https://github.com/gruntwork-io/pipelines-actions/compare/v1.4.0...v1.5.0

v1.4.0

Published: 7/2/2024 | Release notes

feat: plumb through arch catalog configs by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-actions/pull/28
Extract Pipelines install logic into composite action by @oredavids in https://github.com/gruntwork-io/pipelines-actions/pull/29
feat: move gruntwork context to pipelines root from baseline child account by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-actions/pull/30
feat: add pr outputs for delegated repo vending step by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-actions/pull/31
Use the default GH_TOKEN for posting step-summary after account provisioning instead of infra root to align with how we do other comments (DEV-356) by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-actions/pull/32
Custom Action Stubs by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-actions/pull/33

Full Changelog: https://github.com/gruntwork-io/pipelines-actions/compare/v1.3.4...v1.4.0

pipelines-cli

v0.23.1

Published: 7/31/2024 | Release notes

Fix accidental stdout output by @Resonance1584 in https://github.com/gruntwork-io/pipelines/pull/220

Full Changelog: https://github.com/gruntwork-io/pipelines/compare/v0.23.0...v0.23.1

v0.23.0

Published: 7/31/2024 | Release notes

feat: Resolve Configurations Lazily by @yhakbar in https://github.com/gruntwork-io/pipelines/pull/213
feat: Adding latest check by @yhakbar in https://github.com/gruntwork-io/pipelines/pull/217
feat: Adding Linting by @yhakbar in https://github.com/gruntwork-io/pipelines/pull/219
fix: Addressing #213 Review Feedback by @yhakbar in https://github.com/gruntwork-io/pipelines/pull/218
DEV-227 Add segment SDK telemetry by @Resonance1584 in https://github.com/gruntwork-io/pipelines/pull/216

Full Changelog: https://github.com/gruntwork-io/pipelines/compare/v0.22.0...v0.23.0

v0.22.0

Published: 7/24/2024 | Release notes

fix: Check to see if parent terragrunt.hcl is at the root of the repository by @yhakbar in https://github.com/gruntwork-io/pipelines/pull/209
DEV-421 - feat: Expand Automated Configuration Tests by @yhakbar in https://github.com/gruntwork-io/pipelines/pull/211
feat: Hide annotations when they're empty by @yhakbar in https://github.com/gruntwork-io/pipelines/pull/212
chore: Cleaning up helpers updates by @yhakbar in https://github.com/gruntwork-io/pipelines/pull/214
Add sleep when rate limited on github search endpoint by @Resonance1584 in https://github.com/gruntwork-io/pipelines/pull/215

Full Changelog: https://github.com/gruntwork-io/pipelines/compare/v0.21.2...v0.22.0

v0.21.2

Published: 7/23/2024 | Release notes

feat: Enable Terragrunt debug mode when debug checkbox is set in GHA by @yhakbar in https://github.com/gruntwork-io/pipelines/pull/208

Full Changelog: https://github.com/gruntwork-io/pipelines/compare/v0.21.1...v0.21.2

v0.21.1

Published: 7/19/2024 | Release notes

Log tweaks to improve readability @Resonance1584 in https://github.com/gruntwork-io/pipelines/pull/207

Full Changelog: https://github.com/gruntwork-io/pipelines/compare/v0.21.0...v0.21.1

v0.21.0

Published: 7/18/2024 | Release notes

The aws_accounts block has now become a nested configuration in the new aws block. The intention behind this change is to provide a more generic location for storage of AWS configurations.

While this is a breaking change, it is not currently in use by any customers in production.

feat: Nest accounts into aws block by @yhakbar in https://github.com/gruntwork-io/pipelines/pull/206

Full Changelog: https://github.com/gruntwork-io/pipelines/compare/v0.20.0...v0.21.0

v0.20.0

Published: 7/16/2024 | Release notes

feat: Renaming pipelines configuration block to repository by @yhakbar in https://github.com/gruntwork-io/pipelines/pull/205

Full Changelog: https://github.com/gruntwork-io/pipelines/compare/v0.19.3...v0.20.0

v0.19.3

Published: 7/16/2024 | Release notes

Reduce log noise by @Resonance1584 in https://github.com/gruntwork-io/pipelines/pull/204

Full Changelog: https://github.com/gruntwork-io/pipelines/compare/v0.19.2...v0.19.3

v0.19.2

Published: 7/16/2024 | Release notes

DEV-410 Make logs human readable, add github actions log grouping by @Resonance1584 in https://github.com/gruntwork-io/pipelines/pull/203

Full Changelog: https://github.com/gruntwork-io/pipelines/compare/v0.19.1...v0.19.2

v0.19.1

Published: 7/16/2024 | Release notes

fix: Correcting default attributes for the authentication block by @yhakbar in https://github.com/gruntwork-io/pipelines/pull/202

Full Changelog: https://github.com/gruntwork-io/pipelines/compare/v0.19.0...v0.19.1

v0.19.0

Published: 7/16/2024 | Release notes

feat: Renaming plan_iam_role and apply_iam_role to plan_iam_role_arn and apply_iam_role_arn respectively by @yhakbar in https://github.com/gruntwork-io/pipelines/pull/201

Full Changelog: https://github.com/gruntwork-io/pipelines/compare/v0.18.0...v0.19.0

v0.18.0

Published: 7/16/2024 | Release notes

The telemetry disclosure has been removed when running in CI. This warning was a valuable disclosure for some folks, but cluttered the logs and users didn't find it valuable to have the disclosure continuously emitted.

Addressing usage feedback, the following has changed in Pipelines HCL configurations:

The authentication_profile block has been removed. Authentication configurations must now always be directly defined where authentication is specified.
The plan_iam_role and apply_iam_role attributes now utilize fully qualified ARNs instead of just the role name.

DEV-411 Remove telemetry log when running in CI by @Resonance1584 in https://github.com/gruntwork-io/pipelines/pull/199
fix: Remediating drift from spec by @yhakbar in https://github.com/gruntwork-io/pipelines/pull/200

Full Changelog: https://github.com/gruntwork-io/pipelines/compare/v0.17.9...v0.18.0

v0.17.9

Published: 7/12/2024 | Release notes

fix: Adjusting build releases so that more information is communicated to pipelines-cli from this repo by @yhakbar in https://github.com/gruntwork-io/pipelines/pull/196

Full Changelog: https://github.com/gruntwork-io/pipelines/compare/v0.17.8...v0.17.9

v0.17.9-alpha

Published: 7/12/2024 | Release notes

fix: Adjusting build releases so that more information is communicated to pipelines-cli from this repo by @yhakbar in https://github.com/gruntwork-io/pipelines/pull/196

Full Changelog: https://github.com/gruntwork-io/pipelines/compare/v0.17.8...v0.17.9-alpha

v0.17.8

Published: 7/12/2024 | Release notes

Release duplicated from https://github.com/gruntwork-io/pipelines/releases/tag/v0.17.8

v0.17.7

Published: 7/11/2024 | Release notes

Release duplicated from https://github.com/gruntwork-io/pipelines/releases/tag/v0.17.7

v0.17.6-alpha

Published: 7/11/2024 | Release notes

Release duplicated from https://github.com/gruntwork-io/pipelines/releases/tag/v0.17.6-alpha

v0.17.6

Published: 7/11/2024 | Release notes

Release duplicated from https://github.com/gruntwork-io/pipelines/releases/tag/v0.17.6

v0.17.5

Published: 7/10/2024 | Release notes

Release duplicated from https://github.com/gruntwork-io/pipelines/releases/tag/v0.17.5

v0.17.4

Published: 7/10/2024 | Release notes

Release duplicated from https://github.com/gruntwork-io/pipelines/releases/tag/v0.17.4

v0.17.3

Published: 7/10/2024 | Release notes

Release duplicated from https://github.com/gruntwork-io/pipelines/releases/tag/v0.17.3

v0.17.2

Published: 7/10/2024 | Release notes

Release duplicated from https://github.com/gruntwork-io/pipelines/releases/tag/v0.17.2

v0.17.1

Published: 7/10/2024 | Release notes

Release duplicated from https://github.com/gruntwork-io/pipelines/releases/tag/v0.17.1

v0.17.0

Published: 7/9/2024 | Release notes

Release duplicated from https://github.com/gruntwork-io/pipelines/releases/tag/v0.17.0

v0.16.1

Published: 7/9/2024 | Release notes

Release duplicated from https://github.com/gruntwork-io/pipelines/releases/tag/v0.16.1

v0.16.0

Published: 7/8/2024 | Release notes

Release duplicated from https://github.com/gruntwork-io/pipelines/releases/tag/v0.16.0

v0.15.1-alpha2

Published: 7/3/2024 | Release notes

Release duplicated from https://github.com/gruntwork-io/pipelines/releases/tag/v0.15.1-alpha2

v0.15.1-alpha

Published: 7/3/2024 | Release notes

Release duplicated from https://github.com/gruntwork-io/pipelines/releases/tag/v0.15.1-alpha

v0.15.1

Published: 7/3/2024 | Release notes

Release duplicated from https://github.com/gruntwork-io/pipelines/releases/tag/v0.15.1

v0.15.0

Published: 7/3/2024 | Release notes

Release duplicated from https://github.com/gruntwork-io/pipelines/releases/tag/v0.15.0

v0.14.0

Published: 7/2/2024 | Release notes

Release duplicated from https://github.com/gruntwork-io/pipelines/releases/tag/v0.14.0

pipelines-workflows

v2

Published: 7/2/2024 | Release notes

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

v2.5.0

Published: 7/30/2024 | Release notes

DEV-427 - Unlock State Workflow by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-workflows/pull/64
chore: Bumping pipelines to v0.21.2 by @yhakbar in https://github.com/gruntwork-io/pipelines-workflows/pull/65
DEV-129: Add additional pipelines preflight checks by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-workflows/pull/67
Fix action reference in account bootstrap job's name by @oredavids in https://github.com/gruntwork-io/pipelines-workflows/pull/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: https://github.com/gruntwork-io/pipelines-workflows/compare/v2...v2.5.0

v2.4.0

Published: 7/19/2024 | Release notes

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.

chore: Bumping pipelines and pipelines-actions versions by @yhakbar in https://github.com/gruntwork-io/pipelines-workflows/pull/63

Full Changelog: https://github.com/gruntwork-io/pipelines-workflows/compare/v2.3.3...v2.4.0

v2.3.3

Published: 7/16/2024 | Release notes

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.

feat: Bumping pipelines-cli to v0.20.0 and pipelines-actions to v1.8.0 by @yhakbar in https://github.com/gruntwork-io/pipelines-workflows/pull/62

Full Changelog: https://github.com/gruntwork-io/pipelines-workflows/compare/v2...v2.3.3

v2.3.2

Published: 7/16/2024 | Release notes

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

Full Changelog: https://github.com/gruntwork-io/pipelines-workflows/compare/v2...v2.3.2

v2.3.1

Published: 7/16/2024 | Release notes

chore: Bumping pipelines-cli to v0.19.1 by @yhakbar in https://github.com/gruntwork-io/pipelines-workflows/pull/61

Full Changelog: https://github.com/gruntwork-io/pipelines-workflows/compare/v2.3.0...v2.3.1

v2.3.0

Published: 7/16/2024 | Release notes

feat: Adding pipelines.yml workflow by @yhakbar in https://github.com/gruntwork-io/pipelines-workflows/pull/51
chore: Bumping pipelines-cli to v0.19.0 by @yhakbar in https://github.com/gruntwork-io/pipelines-workflows/pull/60
chore: Bumping pipelines-actions to v1.7.0 by @yhakbar in https://github.com/gruntwork-io/pipelines-workflows/pull/59

Full Changelog: https://github.com/gruntwork-io/pipelines-workflows/compare/v2.2.1...v2.3.0

v2.2.1

Published: 7/8/2024 | Release notes

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 https://github.com/gruntwork-io/pipelines-workflows/pull/48
@oredavids made their first contribution in https://github.com/gruntwork-io/pipelines-workflows/pull/48

Full Changelog: https://github.com/gruntwork-io/pipelines-workflows/compare/v2...v2.2.0

v2.1.0

Published: 7/3/2024 | Release notes

Take special note of the changes in https://github.com/gruntwork-io/pipelines-workflows/pull/45. It introduces significant changes to how Pipelines workflows operate, and should be evaluated carefully when considering an upgrade to this release.

In particular, https://github.com/gruntwork-io/pipelines-workflows/pull/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.

fix: Adjusting delegated workflow so that it uses dynamic authentication too by @yhakbar in https://github.com/gruntwork-io/pipelines-workflows/pull/44
feat: Bumping Pipelines CLI to v0.15.1 by @yhakbar in https://github.com/gruntwork-io/pipelines-workflows/pull/45
chore: Pin actions version by @yhakbar in https://github.com/gruntwork-io/pipelines-workflows/pull/46

Full Changelog: https://github.com/gruntwork-io/pipelines-workflows/compare/v1.6.0...v2.1.0

v2.0.0

Published: 7/2/2024 | Release notes

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.

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.

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
Use pipelines auth for terragrunt execute by @Resonance1584 in https://github.com/gruntwork-io/pipelines-workflows/pull/37
chore: add bootstrap to root, make bootstrap step id consistent by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-workflows/pull/41
Fix missed rename by @Resonance1584 in https://github.com/gruntwork-io/pipelines-workflows/pull/42
Customization Hooks by @ZachGoldberg in https://github.com/gruntwork-io/pipelines-workflows/pull/40
fix: Moving yml configurations for custom actions to an action.yml nested under the action name by @yhakbar in https://github.com/gruntwork-io/pipelines-workflows/pull/43