Support to disable rotation of secret manager

[jherrenoitera]

Describe the Feature

When

manage_admin_user_password = true

Its created a secret with automate rotation

Expected Behavior

Varible for disable rotation

Use Case

new feature

Describe Ideal Solution

Varible for disable rotation

Alternatives Considered

No response

Additional Context

No response

[RickArroues]

The aws_rds_cluster resource has a boolean to control manage_admin_user_password. There are no other settings supported. This sort of request would have to go to either AWS to support such a thing or the aws provider if there are further configurations.

But also a managed password of this nature you should expect this sort of behavior. The managed credentials ought to not be used except to create the instance and setup a new role for postgresql administration. Say the role you'd assign further automation and/or hand over to your dba.

The managed master password would be used sparingly and the password retrieved each time it needs used.

That said the new module I'm working on is being tested with setting a managed master credential, retrieving it in the same module to use with the postgresql provider to make a single "admin" role that's not the master, and then all further administration is done on a different postgresql provider to manage postgresql. A little silly with it all batched together and despite it being my architecture based on what was asked of me I'll be suggesting we split into two modules. One to create the instance and the single role. Then the other to use that single role for everything else. Giving us a clear line between setup and management of the instance vs management of postgresql resources. For your consideration.