jbardin
commented
2 years ago Hi @zogamorph,
A tuple's type includes the number of elements, so the error is technically correct, in that the conditional expression contains inconsistent types. The reason these are remaining as tuples is because the individual elements of the collections themselves are not consistently typed, and cannot be converted to a list.
The easiest solution here (though it would take some refactoring to deal with multiple ranges) would be to make each object a simple map(string), which is easier to dynamically populate and merge. If you want to retain the ability to have attributes of different types, it's probably better to declare the values as modules inputs so that explicit type constraints can be set, however that would make things a bit more verbose (at least until there is a solution for optional attributes in place).
Another thing to note here is that because of the mixed object types, some of the values shown here are going to be converted to map(string) converting the numbers to a strings in order to make the expression valid, which may be surprising later on when what is written as a numeric literal shows up as a string when assigned elsewhere.
We use GitHub issues for tracking bugs and enhancements, rather than for questions. While we can sometimes help with certain simple problems here, it's better to use the community forum where there are more people ready to help.
Thanks!
github-actions[bot]
Terraform Version
Terraform Configuration Files
Debug Output
https://gist.github.com/zogamorph/53d7d5072dcb4947da928c01fda36111
Expected Behavior
When IsProductionBuild is ture then expect the RuleSetToApply01 and RuleSetToApply02 to have all the object/maps found in DefaultRuleSet, MainRulesSet and RuleSet1
When IsProductionBuild is false then expect the RuleSetToApply01 and RuleSetToApply02 to have all the object/maps found in DefaultRuleSet, MainRulesSet and RuleSet1 and RuleSet2
Actual Behavior
╷ │ Error: Inconsistent conditional result types │ │ on test.tf line 283, in locals: │ 283: RuleSetToApply01 = local.IsProductionBuild ? concat(local.DefaultRuleSet, local.MainRulesSet, local.RuleSet1) : concat(local.DefaultRuleSet, local.MainRulesSet, local.RuleSet1, local.RuleSet2) │ ├──────────────── │ │ local.DefaultRuleSet is tuple with 2 elements │ │ local.IsProductionBuild is true │ │ local.MainRulesSet is tuple with 18 elements │ │ local.RuleSet1 is tuple with 1 element │ │ local.RuleSet2 is tuple with 1 element │ │ The true and false result expressions must have consistent types. The given expressions are tuple and tuple, respectively. ╵ ╷ │ Error: Inconsistent conditional result types │ │ on test.tf line 284, in locals: │ 284: RuleSetToApply02 = local.IsProductionBuild ? local.FullDefaultRules : concat(local.RuleSet2, local.FullDefaultRules) │ ├──────────────── │ │ local.FullDefaultRules is tuple with 21 elements │ │ local.IsProductionBuild is true │ │ local.RuleSet2 is tuple with 1 element │ │ The true and false result expressions must have consistent types. The given expressions are tuple and tuple, respectively.
Steps to Reproduce
Additional Context
I currently have a module that use the results from concat(local.DefaultRuleSet, local.MainRulesSet, local.RuleSet1).
I now requirement that if we are not in production I need extra rule to applied.
Me and my colleges believe what I am trying to do make sense and we can't workout why it's not working.
References