fix: Fixed error when custom_origin_config is missed and set as optional in a variables schema#161
Closed
baburciu wants to merge 1 commit intoterraform-aws-modules:masterfrom
Closed
Conversation
…nal in a variables schema
Author
|
There are more variables that can fall in such a sanitized_origins = {
for key, origin in local.distribution["origin"] : key => merge(
{
domain_name = origin.domain_name
},
try(origin.custom_origin_config) != null ? { custom_origin_config = origin.custom_origin_config } : {}
)
} |
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Allow for
custom_origin_configto be missed (e.g. we want the CloudFront distribution to only have an S3 Origin with OAC) but also includecustom_origin_configas an optional object in theoriginvariable definition:With this variables schema, if we then don't provide
custom_origin_configin the input,lookup(origin.value, "custom_origin_config", "")function is returning null instead of the empty string that the module expected.Motivation and Context
We get
when
custom_origin_configis missed in aorigin.barinput, ifcustom_origin_configis defined as optional var.Breaking Changes
N/A
How Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectsWe use the module like this:
but we try to enforce a schema for the variables (the
originone in particular here), likeand passing input vars
shows the error for
bar@productionentry (wherecustom_origin_configis missed).pre-commit run -aon my pull request