Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid function argument error seen when use_ibm_owned_encryption_key is true #505

Open
ocofaigh opened this issue Jan 21, 2025 · 2 comments
Assignees

Comments

@ocofaigh
Copy link
Member

Report from consumer:

We are seeing an error in Redis DA v 1.16.1 when use_default_backup_encryption_key is set to true and use_ibm_owned_encryption_key is set to false.

 2025/01/21 17:15:48 Terraform plan | Error: Invalid function argument
 2025/01/21 17:15:48 Terraform plan | 
 2025/01/21 17:15:48 Terraform plan |   on .terraform/modules/redis.redis.backup_key_crn_parser/modules/crn-parser/main.tf line 6, in locals:
 2025/01/21 17:15:48 Terraform plan |    6:   split_crn        = coalescelist(split(":", var.crn))
 2025/01/21 17:15:48 Terraform plan |     ├────────────────
 2025/01/21 17:15:48 Terraform plan |     │ while calling split(separator, str)
 2025/01/21 17:15:48 Terraform plan |     │ var.crn is null
 2025/01/21 17:15:48 Terraform plan | 
 2025/01/21 17:15:48 Terraform plan | Invalid value for "str" parameter: argument must not be null.

I notice we don’t have a test for this use case in redis, yet we have it in Postgres -> https://github.com/terraform-ibm-modules/terraform-ibm-icd-postgresql/blob/658f85201e4f6db42bf2d8306bced803fd883ea8/tests/pr_test.go#L128
This seems to be a test gap that needs to be plugged.

@bsvihovec
Copy link

Hi. Any updates on this one? Thanks.

@jor2
Copy link
Member

jor2 commented Jan 23, 2025

Hi. Any updates on this one? Thanks.

Hi, we are just finalising the PR. Should be ready to go today for release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants