Postgres DA does not allow use_default_backup_encryption_key / use_ibm_owned_encryption_key

[PatrickDuncan]

Hi, I have to provision my Postgres instance using the Deployable Architecture. For some reason existing_kms_instance_crn is a required parameter that then makes using use_default_backup_encryption_key impossible since they are mutually exclusive. The variable descriptions detail the mutually exclusion clearly. So it seems to me like a bug in the DA definition.

Affected modules

• Postgres

Expected behavior

The change should be to make existing_kms_instance_crn optional.

[ocofaigh]

@PatrickDuncan existing_kms_instance_crn is not a required variable. It has a default value of null.
The input shows in the required tab of projects because we want to encourage users to use KMS encryption. But you can leave it with its default value of null.
Can you confirm it works if you leave it as null ?

[PatrickDuncan]

Value must be __NULL__ which is the default that can be reset after hovering over the input value. A little un-intuitive experiencing this for the first time, but makes sense to me now. Thanks