chore(deps): update terraform github.com/cloudposse/terraform-aws-rds-cluster to v0.50.2 #33

red-hat-konflux · 2025-05-09T10:13:13Z

This PR contains the following updates:

Package	Type	Update	Change
github.com/cloudposse/terraform-aws-rds-cluster	module	minor	`tags/0.36.0` -> `0.50.2`

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

Release Notes

cloudposse/terraform-aws-rds-cluster (github.com/cloudposse/terraform-aws-rds-cluster)

`v0.50.2`

Compare Source

🚀 Enhancements

Add optional `subnet_group_name` input to override the name @tjarjoura (#133)

what

Allow the user to specify the db_subnet_group name, rather than using the default label ID

why

If importing an existing database cluster and subnet group, we need to be able to set the subnet group name to what it already has, otherwise the subnet group will be recreated. This in turn will cause the database cluster to be recreated, which we don't want.

references

https://sweetops.slack.com/archives/CB6GHNLG0/p1646336110444589

`v0.50.1`

Compare Source

🚀 Enhancements

Add enhanced monitoring attributes @nitrocode (#131)

what

Add enhanced monitoring attributes

why

The name can be too long at times and exposing this input could prevent the following error

│ Error: expected length of name to be in the range (1 - 64), got snip-snip-snip-snip-aurora-global-example-shared-enhanced-monitoring
│
│   with module.primary_aurora_postgres_cluster.aws_iam_role.enhanced_monitoring[0],
│   on .terraform-mdev/modules/primary_aurora_postgres_cluster/enhanced-monitoring.tf line 17, in resource "aws_iam_role" "enhanced_monitoring":
│   17:   name               = module.enhanced_monitoring_label.id

references

`v0.50.0`

Compare Source

Add support for disabling egress traffic @jalgraves (#130)

what

Add support for disabling egress security-group rule in default security group

why

tl;dr My boss told me to.

We had a third party do a pen test and afterwards they suggested we remove egress traffic from our DB subnets. If I'm missing something and there is another way to accomplish this without changing the module I'd be happy and grateful to hear it.

`v0.49.2`

Compare Source

🚀 Enhancements

Create dns record if not serverless @nitrocode (#128)

what

Restore original logic

why

Previous logic was to create the record when module was not serverless

references

Previous PR https://github.com/cloudposse/terraform-aws-rds-cluster/pull/124

`v0.49.1`

Compare Source

🚀 Enhancements

Flag `master_username` output as sensitive @batistadasilva (#114)

what

Flag master_username output as sensitive

why

Running on Terraform Cloud

Terraform v0.14.5
Configuring remote state backend...
Initializing Terraform configuration...

Error: Output refers to sensitive values

  on .terraform/modules/db/outputs.tf line 6:
   6: output "master_username" {

Expressions used in outputs can only refer to sensitive values if the
sensitive attribute is true.

references

https://www.terraform.io/upgrade-guides/0-14.html#sensitive-values-in-plan-output

`v0.49.0`

Compare Source

fix: prevent creating empty replicas record @syphernl (#126)

what

Prevent creating empty DNS replicas record when cluster_size < 1

why

If the cluster_size = 0 this would result in an attempt to create an empty DNS record, which is not permitted by the Route53 API

references

Follow-up to changes done in https://github.com/cloudposse/terraform-aws-rds-cluster/pull/124

`v0.48.1`

Compare Source

🚀 Enhancements

Update AWS provider minimum version @alexjurkiewicz (#125)

what

c96d859 added performance_insights_retention_period, which is supported in AWS provider v3.63.0 onwards.

why

Prevent issues with older cached aws providers

references

N/A

`v0.48.0`

Compare Source

Additional inputs @nitrocode (#124)

what

Add performance_insights_retention_period
Add ca_cert_identifier
Add preferred_maintenance_window to instances
Add timeout to instances

why

Performance insights retention
Add a ca cert identifier
Put the maintenance window on cluster and instances
Allow rds instances to be created without hitting a timeout

`v0.47.2`

Compare Source

🤖 Automatic Updates

chore(deps): update terraform cloudposse/label/null to v0.25.0 @renovate (#122)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/label/null (source)	module	minor	`0.24.1` -> `0.25.0`

Release Notes

cloudposse/terraform-null-label

`v0.25.0`

Compare Source

Add "tenant", "labels_as_tags", and "descriptors" @Nuru (#132)

what

Add additional label and id component: tenant
New input labels_as_tags controls which labels are exported as tags
New input descriptor_formats generates new output descriptors
Update README, remove link to obsolete terraform-terraform-label

why

Support users that host resources on behalf of and/or dedicated to single customers
Supersedes and closes #131, giving people control over which tags the module generates
Simple mechanism for creating multiple identifiers from the same inputs, reducing the need to create multiple instances of null-label
Document tenant, labels_as_tags, descriptor_formats, add additional clarification, stop promoting obsolete module

Fix: Update README Snippets @korenyoni (#130)

what

Update README snippets to reflect use of Terraform Registry.

why

Including snippets that reflect use of the Terraform Registry make it easier for users to quickly instantiate a null_label module.
README is out of date and does not include snippets that reflect use of the Terraform Registry.

references

N/A

Bridgecrew compliance @Nuru (#125)

what

Resolve Bridgecrew compliance complaint about example Autoscaling Group (BC_AWS_GENERAL_31)
Fix typo in README
Include Terraform lock file in .gitignore

why

Get clean Bridgecrew badge
Correct confusing error
Ensure lock files are not checked into GitHub

note

The PR can and should be merged into master to update README and Bridgecrew without triggering a new release/version. These changes have no effect on the actual module in use and a release will create unnecessary ripple effects. However, merging to master will update the README and badges, so is worthwhile, and the changes will move forward into the next release.

Properly output descriptors of chained modules @Nuru (#133)

what

Properly output descriptors of chained modules

why

Bug fix; implement intended behavior

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

`v0.47.1`

Compare Source

🤖 Automatic Updates

chore(deps): update terraform cloudposse/route53-cluster-hostname/aws to v0.12.2 @renovate (#121)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/route53-cluster-hostname/aws (source)	module	patch	`0.12.0` -> `0.12.2`

Release Notes

cloudposse/terraform-aws-route53-cluster-hostname

`v0.12.2`

Compare Source

🚀 Enhancements

Bump AWS provider 3.0 @nitrocode (#36)

what

Bump AWS provider 3.0

why

Downstream modules can take advantage of the more recent aws provider

references

N/A

`v0.12.1`

Compare Source

🚀 Enhancements

Chore: run `make github/init` @korenyoni (#37)

what

Run make github/init.

why

Updates GHA-workflow-related files to their latest distribution.
The old context.tf distribution is incompatible with the tenant label.

references

https://github.com/cloudposse/terraform-null-label/releases/tag/0.25.0

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

`v0.47.0`

Compare Source

Ignore admin credentials for snapshots/replicated clusters @alexjurkiewicz (#119)

Fixes errors like:

Error: error creating RDS cluster: InvalidParameterCombination: Cannot specify user name for instance cluster replication cluster

`v0.46.2`

Compare Source

🤖 Automatic Updates

Update context.tf @cloudpossebot (#118)

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.

`v0.46.1`

Compare Source

🚀 Enhancements

added apply_immediately support to cluster_instance resource @RichardHeywood (#111)

what

Add apply_immediately flag to the db instances

why

Currently you can only apply changes immediately to the cluster resource. However the aws_rds_cluster_instance resource also supports the apply_immediately flag.
Use case: Attempting to change the instance types for the RDS cluster causes the changes to be staged pending the next maintenance window. This change allows you to perform the updates before then.

`v0.46.0`

Compare Source

Ignore `engine_version` for rds instance in order to upgrade without recreating db instances @nitrocode (#115)

what

Ignore engine_version for rds instance in order to upgrade

why

When the engine_version for the aws_rds_cluster is changed and applied, the db instances will be upgraded.
There is a note on the rds_cluster_instance#engine_version which states

(Optional, Forces new resource) The database engine version. When managing the engine version in the cluster, it is recommended to add the lifecycle ignore_changes configuration for this argument to prevent Terraform from proposing changes to the instance engine version directly.

terraform plan

### module.primary_aurora_postgres_cluster.aws_rds_cluster_instance.default[0] must be replaced
+/- resource "aws_rds_cluster_instance" "default" {
      + apply_immediately               = (known after apply)
      ~ arn                             = "arn:aws:rds:us-east-2:snip:db:snip-1" -> (known after apply)
      ~ availability_zone               = "us-east-2c" -> (known after apply)
      ~ ca_cert_identifier              = "rds-ca-2019" -> (known after apply)
      ~ dbi_resource_id                 = "db-snip" -> (known after apply)
      ~ endpoint                        = "snip-1.snip.us-east-2.rds.amazonaws.com" -> (known after apply)
      ~ engine_version                  = "12.4" -> "12.6" # forces replacement
      ~ id                              = "snip-1" -> (known after apply)
      + identifier_prefix               = (known after apply)
      ~ kms_key_id                      = "arn:aws:kms:us-east-2:snip:key/snip" -> (known after apply)
      + monitoring_role_arn             = (known after apply)
      + performance_insights_kms_key_id = (known after apply)
      ~ port                            = 5432 -> (known after apply)
      ~ preferred_backup_window         = "07:00-09:00" -> (known after apply)
      ~ preferred_maintenance_window    = "sun:07:32-sun:08:02" -> (known after apply)
      ~ storage_encrypted               = true -> (known after apply)
      ~ writer                          = true -> (known after apply)

### (13 unchanged attributes hidden)
    }

terraform apply (error)

module.primary_aurora_postgres_cluster.aws_rds_cluster_instance.default[0]: Creating...
╷
│ Error: error creating RDS Cluster (snip) Instance: DBInstanceAlreadyExists: DB Instance already exists
│ 	status code: 400, request id: snip
│ 
│   with module.primary_aurora_postgres_cluster.aws_rds_cluster_instance.default[0],
│   on main.tf line 206, in resource "aws_rds_cluster_instance" "default":
│  206: resource "aws_rds_cluster_instance" "default" {
│ 
╵

terraform plan (no changes)

Note: Objects have changed outside of Terraform

Terraform detected the following changes made outside of Terraform since the last "terraform
apply":

### module.primary_aurora_postgres_cluster.aws_rds_cluster_instance.default[0] has been changed
  ~ resource "aws_rds_cluster_instance" "default" {
      ~ engine_version               = "12.4" -> "12.6"
        id                           = "snip-1"

### (24 unchanged attributes hidden)
    }

Unless you have made equivalent changes to your configuration, or ignored the relevant
attributes using ignore_changes, the following plan may include actions to undo or respond to
these changes.

No changes. Your infrastructure matches the configuration.

Confirmed in the AWS console that the postgres aurora rds instance and cluster are 12.6.

references

N/A

`v0.45.0`

Compare Source

allow major version upgrades @kevcube (#113)

what

enables upgrading major versions (closes #87)

why

sometimes ya gotta upgrade major versions

references

`v0.44.2`

Compare Source

🚀 Enhancements

fix: 🐛 adjust engine version in docs and readme to aurora-mysql @sheldonhull (#112)

what

Prior value was invalid according to aws docs when trying to create a aurora-mysql based instance.

AWS Terraform Provider docs indicated:

engine - (Optional) The name of the database engine to be used for this DB cluster. Defaults to aurora. Valid Values: aurora, aurora-mysql, aurora-postgresql

Since the examples I used were to deploy aurora-mysql the engine should be set to this as well when the cluster family is set as follows:

engine  = "aurora-mysql"
cluster_family  = "aurora-mysql5.7"

why

Adjust to aurora-mysql and this resolved the failure to deploy a new cluster based on the mysql engine.

`v0.44.1`

Compare Source

🚀 Enhancements

create_before_destroy for parameter groups, explicit dependencies @Nuru (#110)

what

Make parameter groups create_before_destroy
Add explicit dependencies

why

You cannot delete a parameter group while it is in use, but you can update a database with a new parameter group, so in order to change parameter groups, you need to create a new one, install it, then delete the old one.
Some update and destroy operations were failing because resources were being deleted in the wrong order.

`v0.44.0`

Compare Source

Be explicit about creating a regional (standalone) cluster or one part of a Global cluster @Nuru (#109)

what

replace make_primary_cluster with cluster_type

why

The name "make_primary_cluster" was very misleading

`v0.43.0`

Compare Source

The variable introduced in this release (make_primary_cluster) was poorly named, leading to significant confusion. It was replaced with a new variable, cluster_type, in the next release. Therefore this release is not recommended for use.

Be explicit about primary/secondary cluster @Nuru (#108)

what

Allow user to specify explicitly whether or not this should create a primary or secondary cluster

why

Implicit selection based on global_cluster_identifier fails if the global cluster is being created at the same time as the primary and/or secondary cluster

`v0.42.1`

Compare Source

🤖 Automatic Updates

Update Terraform cloudposse/route53-cluster-hostname/aws to v0.12.0 @renovate (#106)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/route53-cluster-hostname/aws (source)	terraform	minor	`0.11.0` -> `0.12.0`

Release Notes

cloudposse/terraform-aws-route53-cluster-hostname

`v0.12.0`

Compare Source

context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @maximmi (#35)

what

update context.tf to v0.24.1
minimum required Terraform version bumped to 0.13.0
readme updated, Bridgecrew compliance badges added

why

It allows for setting the letter case of tag names and labels, back compatibility with context v0.22.0 and below
we have dropped support for Terraform 0.12
To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

`v0.42.0`

Compare Source

No changes

`v0.41.1`

Compare Source

🤖 Automatic Updates

Update Terraform cloudposse/label/null to v0.24.1 @renovate (#102)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/label/null (source)	terraform	minor	`0.22.0` -> `0.24.1`

Release Notes

cloudposse/terraform-null-label

`v0.24.1`

Compare Source

Allow control of letter case of outputs @SweetOps (#107)

You now have control over the letter case of generated tag names and supplied labels, which means you also have control over the letter case of the ultimate id.

Labels are the elements you can include in label_order, namely namespace, environment, stage, name, and attributes. For every non-empty label, a corresponding tag name is generated. For namespace, environment, stage, the output is the formatted, normalized input. (By "normalized" we mean that it goes through regex_replace_chars.), For attributes, which is a list, each element is normalized, duplicates are removed, and the resulting list is converted to a string by joining the elements with the delimiter (defaults to hyphen). For name, which is special, the output is the same as id, which is the joining of the labels in the order specified by label_order and separated by delimiter.

You can set label_key_case to one of upper, lower, or title, which will result in generated tag names in the corresponding case: NAME, name, or Name. For backwards compatibility, title is the default
You can set label_value_case to one of upper, lower, title, or none, which will result in output label values in the corresponding case (with none meaning no case conversion of any kind will be done, though the labels will still be subject to regex_replace_chars). The case converted labels will show up not just in the module output of the labels themselves, but also in the tag values and in the id string.

You can look at the test cases in examples/complete and the expected results in test/src/examples_complete_test.go to see examples of how this is supposed to work.

One interesting example is that you can create ids in Pascal case by setting label_value_case = "title" and delimiter = "".

Include updates to exports/context.tf @Nuru (#122 and #123)

what

Include updates to exports/context.tf
Update README with features and compatibilty
Add validation for id_length_limit

why

The exports/context.tf is what gets distributed and needs to be in sync
Replace outdated information
Was not validated earlier because validators are not supported in TF 0.12 but now we are dropping support for TF 0.12 and so we can add validators

Restore backward compatibility with v0.22.1 and earlier @Nuru (#121)

what

Restore backward compatibility with v0.22.1 and earlier
Allow setting of label_key_case and label_value_case by vars, not just by context attributes.

why

Allow interoperability of old and new modules
Normally, root modules make settings via individual variables, not by setting an entire context block.

Incorporates and closes #120

`v0.24.0`

Compare Source

Restore backward compatibility with v0.22.1 and earlier @Nuru (#121)

what

Restore backward compatibility with v0.22.1 and earlier
Allow setting of label_key_case and label_value_case by vars, not just by context attributes.

why

Allow interoperability of old and new modules
Normally, root modules make settings via individual variables, not by setting an entire context block.

Incorporates and closes #120

Allow control of letter case of outputs @SweetOps (#107)

You now have control over the letter case of generated tag names and supplied labels, which means you also have control over the letter case of the ultimate id.

Labels are the elements you can include in label_order, namely namespace, environment, stage, name, and attributes. For every non-empty label, a corresponding tag name is generated. For namespace, environment, stage, the output is the formatted, normalized input. (By "normalized" we mean that it goes through regex_replace_chars.), For attributes, which is a list, each element is normalized, duplicates are removed, and the resulting list is converted to a string by joining the elements with the delimiter (defaults to hyphen). For name, which is special, the output is the same as id, which is the joining of the labels in the order specified by label_order and separated by delimiter.

You can set label_key_case to one of upper, lower, or title, which will result in generated tag names in the corresponding case: NAME, name, or Name. For backwards compatibility, title is the default
You can set label_value_case to one of upper, lower, title, or none, which will result in output label values in the corresponding case (with none meaning no case conversion of any kind will be done, though the labels will still be subject to regex_replace_chars). The case converted labels will show up not just in the module output of the labels themselves, but also in the tag values and in the id string.

You can look at the test cases in examples/complete and the expected results in test/src/examples_complete_test.go to see examples of how this is supposed to work.

One interesting example is that you can create ids in Pascal case by setting label_value_case = "title" and delimiter = "".

`v0.23.0`

Compare Source

feat: add support for setting letter case of context tags @SweetOps (#107)

With this release, you gain control over the letter case of generated tag names and supplied labels, which means you also have control over the letter case of the ultimate id.

Labels are the elements you can include in label_order, namely namespace, environment, stage, name, and attributes. For every non-empty label, a corresponding tag name is generated. For namespace, environment, stage, the output is the formatted, normalized input. (By "normalized" we mean that it goes through regex_replace_chars.), For attributes, which is a list, each element is normalized, duplicates are removed, and the resulting list is converted to a string by joining the elements with the delimiter (defaults to hyphen). For name, which is special, the output is the same as id, which is the joining of the labels in the order specified by label_order and separated by delimiter.

You can set label_key_case to one of upper, lower, or title, which will result in generated tag names in the corresponding case: NAME, name, or Name. For backwards compatibility, title is the default
You can set label_value_case to one of upper, lower, title, or none, which will result in output label values in the corresponding case (with none meaning no case conversion of any kind will be done, though the labels will still be subject to regex_replace_chars). The case converted labels will show up not just in the module output of the labels themselves, but also in the tag values and in the id string.

You can look at the test cases in examples/complete and the expected results in test/src/examples_complete_test.go to see examples of how this is supposed to work.

One interesting example is that you can create ids in Pascal case by setting label_value_case = "title" and delimiter = "".

`v0.22.1`

Compare Source

Add var.attributes to end of context.attributes, not vice versa @Nuru (#114)

what

Add var.attributes to end of context.attributes, not vice versa
Update to current workflows (with some exceptions)

why

Modules should append to attributes passed in, not insert themselves ahead of others
New features, like auto-format (but holding back some, because this is a special module)

references

closes #113
closes #108

Update Terraform cloudposse/route53-cluster-hostname/aws to v0.11.0 @renovate (#103)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/route53-cluster-hostname/aws (source)	terraform	minor	`0.8.0` -> `0.11.0`

Release Notes

cloudposse/terraform-aws-route53-cluster-hostname

`v0.11.0`

Compare Source

minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#34)

what

update context.tf to v0.23.0
minimum required Terraform version bumped to 0.13.0
readme updated, Bridgecrew compliance badges added

why

It allows for setting the letter case of tag names and labels
we have dropped support for Terraform 0.12
To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

`v0.10.1`

Compare Source

🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#33)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

`v0.10.0`

Compare Source

Terraform 0.14 upgrade @maximmi (#32)

what

Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

Support Terraform 0.14

`v0.9.0`

Compare Source

Update `context.tf` and github actions @htplbc (#31)

what

Update to context.tf

why

Keep the module up to date

`v0.41.0`

Compare Source

context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @maximmi (#104)

what

update context.tf to v0.24.1
minimum required Terraform version bumped to 0.13.0
readme updated, Bridgecrew compliance badges added

why

It allows for setting the letter case of tag names and labels, back compatibility with context v0.22.0 and below
we have dropped support for Terraform 0.12
To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

`v0.40.1`

Compare Source

🤖 Automatic Updates

Update context.tf @cloudpossebot (#105)

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.

`v0.40.0`

Compare Source

minimum required Terraform version bumped to 0.13.0, context.tf updated, readme updated @maximmi (#101)

what

update context.tf to v0.23.0
minimum required Terraform version bumped to 0.13.0
readme updated, Bridgecrew compliance badges added

why

It allows for setting the letter case of tag names and labels
we have dropped support for Terraform 0.12
To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

`v0.39.0`

Compare Source

Terraform 0.14 upgrade @maximmi (#98)

what

Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

Support Terraform 0.14

`v0.38.0`

Compare Source

Support for cluster cloning requires AWS provider 3.1.15+ @bazbremner (#96)

what and why

v0.37.0 of this module added support for Aurora cluster cloning and
point-in-time restore [1] which itself was introduced in version
3.1.15 of the AWS provider[2] via the restore_to_point_in_time[3]
attribute.

This commits the dependancy on this module to track that requirement
for the newer AWS provider.

references

[1]https://github.com/cloudposse/terraform-aws-rds-cluster/pull/922
[2] https://github.com/hashicorp/terraform-provider-aws/blob/master/CHANGELOG.md#3150-november-12-2020
[https://github.com/hashicorp/terraform-provider-aws/pull/7031031

`v0.37.1`

Compare Source

🚀 Enhancements

Terraform 0.14 upgrade @woz5999 (#95)

what

fixes and updates for tf 0.14 compatibility

`v0.37.0`

Compare Source

Add suport for cluster cloning @jamengual (#92)

what

Adding cluster clone support

why

in aws provider 3.1.15 clone support was added

references

https://github.com/hashicorp/terraform-provider-aws/issues/5286

Configuration

📅 Schedule: Branch creation - "after 5am on friday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.

This PR has been generated by MintMaker (powered by Renovate Bot).

…-cluster to v0.50.2 Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>

openshift-ci · 2025-05-09T10:13:20Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: red-hat-konflux[bot]
Once this PR has been reviewed and has the lgtm label, please assign franciscojavierarceo for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

openshift-ci · 2025-05-09T10:13:25Z

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a opendatahub-io member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

chore(deps): update terraform github.com/cloudposse/terraform-aws-rds…

099c5d3

…-cluster to v0.50.2 Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>

openshift-ci bot requested review from amsharma3 and franciscojavierarceo May 9, 2025 10:13

openshift-ci bot added the needs-ok-to-test label May 9, 2025

chore(deps): update terraform github.com/cloudposse/terraform-aws-rds-cluster to v0.50.2 #33

Are you sure you want to change the base?

chore(deps): update terraform github.com/cloudposse/terraform-aws-rds-cluster to v0.50.2 #33

Uh oh!

Conversation

red-hat-konflux bot commented May 9, 2025

Release Notes

🚀 Enhancements

what

why

references

🚀 Enhancements

what

why

references

what

why

🚀 Enhancements

what

why

references

🚀 Enhancements

what

why

references

what

why

references

🚀 Enhancements

what

why

references

what

why

🤖 Automatic Updates

Release Notes

what

why

what

why

references

what

why

note

what

why

Configuration

🤖 Automatic Updates

Release Notes

🚀 Enhancements

what

why

references

🚀 Enhancements

what

why

references

Configuration

🤖 Automatic Updates

what

why

🚀 Enhancements

what

why

what

why

references

what

why

references

🚀 Enhancements

what

why

🚀 Enhancements

what

why

what

why

what

why