-
Notifications
You must be signed in to change notification settings - Fork 3
fix: bug with validation #383
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
Conversation
|
/run pipeline |
modules/fscloud/variables.tf
Outdated
| validation { | ||
| condition = anytrue([ | ||
| var.backup_encryption_key_crn == null, | ||
| can(regex(".*kms.*", var.kms_key_crn)), | ||
| can(regex(".*hs-crypto.*", var.kms_key_crn)), | ||
| can(regex(".*kms.*", var.backup_encryption_key_crn)), | ||
| can(regex(".*hs-crypto.*", var.backup_encryption_key_crn)), | ||
| ]) | ||
| error_message = "Value must be the KMS key CRN from a Key Protect or Hyper Protect Crypto Services instance in one of the supported backup regions." | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this whole validation provide any value. It will always be validated in the main module.
|
/run pipeline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this should be changing common-dev-assets.
…raform-ibm-icd-elasticsearch into fix-validation
|
/run pipeline |
|
/run pipeline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
🎉 This PR is included in version 1.25.13 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Description
there is a bug with variable validation referencing incorrect variable.
Release required?
x.x.X)x.X.x)X.x.x)Release notes content
fix bug with variable validation.
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers