-
Notifications
You must be signed in to change notification settings - Fork 0
refactor: Update variable handling to correctly support null for dns_config_name and ca_config_name #282
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 |
|
/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.
This is not what I intended during the discussion. Sorry to have caused confusion.
The aim was to allow null to be passed, not necessarily to default to null. So I was thinking original code
ca_config_name = "${local.prefix}${var.ca_config_name}"
was passing "" or "$local.prefix" when var.ca_config_name was set to null by the consumer. That would likely cause an error.
Thus a likely fix (and doing the same for dns_config_name)
dns_config_name = dns_config_name == null ? null : "${local.prefix}${var.dns_config_name}"
ca_config_name = ca_config_name == null ? null : "${local.prefix}${var.ca_config_name}"
This module can add one CA config, one DNS config, or one of both. Thus it accepts nulls to support the just one scenarios. The DA by default adds one of both.
|
/run pipeline |
|
/run pipeline |
|
/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.
Looks good to me.
|
🎉 This PR is included in version 1.2.4 🎉 The release is available on:
Your semantic-release bot 📦🚀 |

Description
Changed the variable handling of
ca_config_nameso that the default value isnull.Release required?
x.x.X)x.X.x)X.x.x)Release notes content
Changed the variable handling of
ca_config_nameso that the default value isnull.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