Releases: cloudposse/terraform-aws-mwaa
Releases · cloudposse/terraform-aws-mwaa
v0.6.4
🤖 Automatic Updates
v0.6.3
Delete .github/workflows/auto-format.yml @goruha (#55)
what
- Remove
auto-format
workflow
why
- Get rid of
pull_request_target
because of security reason - Auto format workflows are deprecated and already removed from all other repos
🤖 Automatic Updates
v0.6.2
v0.6.1
🤖 Automatic Updates
Update GitHub workflows @osterman (#50)
what
- Update workflows (
.github/workflows/settings.yaml
)
why
- Support new readme generation workflow.
- Generate banners
Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#49)
what
- Install latest GitHub Action Workflows
why
- Use shared workflows from
cldouposse/.github
repository - Simplify management of workflows from centralized hub of configuration
v0.6.0
AWS MWAA Startup Script @DustyShap (#36)
What
Add startup_script_s3_path and startup_script_s3_object_version arguments to the module to be able use these options from aws_mwaa_environment terraform resource.
Why
We need to be able to pull secrets into the AWS MWAA Environment, set connection strings, etc, by way of a bash script that runs before MWAA environment starts
v0.5.0
- No changes
v0.4.8
🚀 Enhancements
Fix Security Group Outputs @milldr (#24)
what
compact()
module.mwaa_security_group.*
outputs
why
- Fix edge case error:
│ Error: Invalid function argument
│
│ on .terraform-x/modules/mwaa_environment/outputs.tf line 52, in output "security_group_arn":
│ 52: value = join("", module.mwaa_security_group.*.arn)
│ ├────────────────
│ │ module.mwaa_security_group is object with 4 attributes
│
│ Invalid value for "lists" parameter: element 0 is null; cannot concatenate null values.
╵
v0.4.7
🤖 Automatic Updates
chore(deps): update terraform cloudposse/security-group/aws to v1.0.1 @renovate (#23)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/security-group/aws (source) | module | patch | 1.0.0 -> 1.0.1 |
v0.4.6
🤖 Automatic Updates
chore(deps): update terraform cloudposse/security-group/aws to v1 @renovate (#22)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/security-group/aws (source) | module | major | 0.4.3 -> 1.0.0 |
v0.4.5
🤖 Automatic Updates
chore(deps): update terraform cloudposse/s3-bucket/aws to v2.0.1 @renovate (#21)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/s3-bucket/aws (source) | module | patch | 2.0.0 -> 2.0.1 |
Release Notes
cloudposse/terraform-aws-s3-bucket
v2.0.1
git.io->cloudposse.tools update @dylanbannon (#149)
#### what and why Change all references to `git.io/build-harness` into `cloudposse.tools/build-harness`, since `git.io` redirects will stop working on April 29th, 2022. #### References - DEV-143Use object lock enabled @nitrocode (#148)
#### what * Use object lock enabled #### why * Deprecation of dynamic `object_lock_configuration` for `object_lock_enabled`│ Warning: Argument is deprecated
│
│ with module.bucket.aws_s3_bucket.default,
│ on .terraform/modules/bucket/main.tf line 30, in resource "aws_s3_bucket" "default":
│ 30: resource "aws_s3_bucket" "default" {
│
│ Use the top-level parameter object_lock_enabled and the aws_s3_bucket_object_lock_configuration resource instead
references
- https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3\_bucket#object_lock_enabled
- Previous PR https://github.com/cloudposse/terraform-aws-s3-bucket/pull/144 (this did not use
object_lock_enabled
and only removed the dynamic)