[v20.3.2] 2025-12-04 [Backport]
Please note changes in 20.3.2 may not yet be released in future versions, as this is a backport and patch release on the 20.3.x series of releases. Updates that are included in the future will have a corresponding CHANGELOG entry in future releases.
Added
- CUMULUS-4354
- Added an optional terraform-configurable lambda level env variable
allow_provider_mismatch_on_rule_filtertomessage-consumerandsqs-message-consumerto check
whether to consider rule/message provider mismatches - Added a
rule.meta.allowProviderMismatchOnRuleFiltercheck tofilterRulesByRuleParamsas a rule-level fallback to check
whether to consider rule/message provider mismatches for the specific rule
- Added an optional terraform-configurable lambda level env variable
Changed
- CUMULUS-4272
- The
tf-modules/cumulus-rds-tfmodule now allows specifying an existing security group.
This enhancement enables DAACs to migrate their existing RDS deployments to Aurora while
reusing their existing security group, ensuring compatibility with existing
data-persistence-tfandcumulus-tfmodules.
- The
Fixed
- CUMULUS-4279
- Updated the
ProvisionPostgresDatabaseLambda to grantcreateandusageprivileges
on the public schema of the user database to the database user.
This change is required because, starting with PostgreSQL 15, new databases assign ownership
of the public schema to the pg_database_owner role. Existing clusters upgraded from versions
prior to v15 preserve the previous ownership of the public schema.
- Updated the
- CUMULUS-4275
- Fixed unit tests broken by updated HTTP error messages in got