Releases: gruntwork-io/pipelines-workflows
v3.5.0
a77b6ca
ZachGoldberg
Zach Goldberg
What's New
This release contains an update to account factory to forward the boolean values disable_macie disable_security_hub and disable_guardduty from the new account request files to the accounts.yml file. This allows terragrunt units in infra-live to more easily access these three per-account configuration options and adjust their inputs appropriately.
Namely, in terraform-aws-architecture-catalog v2.12.0 we update the functionality of the logs account to read these values and disable the macie and security_hub modules, which prevents invites from being sent to accounts that don't have those features enabled. This isn't strictlty required, as previously the invites were sent and never accepted, but this reduces the number of resources provisioned and makes the real world infrastructure better match the intent of the IaC.
Changelog
Bump to pipelines-actions v3.3.0
Full Changelog: v3...v3.5.0
v3
a77b6ca
ZachGoldberg
Zach Goldberg
This is a floating release tracking the latest v3.y.z release.
v3.4.0
b268453
Resonance1584
Lewis Christie
What's Changed
- Fixed a bug where changes to Pipelines Configurations as Code would trigger pipelines plan / apply to be run. These operations were no-ops as no infrastructure was changed, but were unnecessarily using github action minutes.
- Improved startup time for PipelinesCLI by removing terragrunt/tofu/terraform version checks when not running execute. This improves overall pipelines run time.
v3.3.0
Release Notes
Pipelines uses a concept of "Gruntwork Context" which is basically a large bundle of runtime context and pipelines configuration. Generating this context was several hundred lines of bash which included both simple read-and-store logic as well as sophisticated business logic. That code hard to test and a source of many bugs. This release includes a new implementation of all of that logic built into our pipelines binary (written in GoLang), which allows us to unit test the behavior and drive performance improvements over time.
Customers will likely not notice any chance with this release other than maybe 1-2 faster runs in some cases, and ideally fewer corner-case bugs based on less commonly used configurations.
What's Changed
- DEV-663: Bump version of actions that uses binary for reading config by @ZachGoldberg in #100
Full Changelog: v3...v3.3.0
Contributors
Assets 2
v3.2.1
Contributors
Assets 2
v3.2.0
What's Changed
- Record a job start time at the beginning of jobs by @ZachGoldberg in #95
Full Changelog: v3...v3.2.0
Contributors
Assets 2
v3.1.0
What's Changed
- Pipelines CLI v0.31.0 by @Resonance1584 in #93
New Features
Detect changes based on dependent HCL files (Pipelines CLI v.0.31)
If your terragrunt.hcl files use include {} blocks to bring in data from other HCL files, pipelines will now detect if those hcl files are changed and trigger a HCL Changed event which will run a run-all plan with --terragrunt-modules-that-include argument pointed to the changed HCL file. This is currently limited to only work with the include block, we plan to address other methods of nesting configuration such as read_terragrunt_config in a later release.
Fixes & Improvements
- Bootstrap will now correctly detect missing configuration values in
.gruntwork/config.yml. Previously empty values would be passed through which caused issues with templating new accounts. - AWS credentials are now cached which significantly reduces the number of calls made to AWS APIs during a run-all
Full Changelog: v3...v3.1.0
