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
"Error in function call" when using neither private subnets nor NAT #944
Comments
I'm receiving the exact error as well albeit on version |
Same here with v5.0.0 |
I had the same issue. Moreover it does not happen when you run apply with
|
I specifically don't want to enable |
This issue has been automatically marked as stale because it has been open 30 days |
Not fixed, as far as I know, so it may be stale but should not be closed IMHO. |
This issue has been automatically marked as stale because it has been open 30 days |
Why there are no fixes provided for this ticket? There should be mention of steps to take when migrating from v3 to v4. The problem with So I have no idea how impactful this will be to delete the private route tables and use database route tables but in the end, I don't want to have anything like this being deleted during migration. :) If anyone can provide a right fix for that, it will be awesome. |
This issue has been automatically marked as stale because it has been open 30 days |
Not stale, still waiting for a fix. |
I'm experiencing the same issue. I have create_database_subnet_route_table set to true but the problem persist. |
+1 on this, tried to upgrade 3.19.0 -> 5.4.0, |
Is there any update on this? I'm trying to create a private subnet only but get the same issue. |
Description
TF errors out when trying to create a VPC with database subnets but no private subnets and no NAT gateways:
Call to function "coalescelist" failed: no non-null arguments
.It seems that the
aws_route_table.private
isn't created in this case (percount
condition), but it is apparently meant to be referenced inaws_route_table_association.database
.Versions
Module version [Required]: 5.0.0
Terraform version: 1.4.6
Provider version(s): 5.0.1
Reproduction Code [Required]
Expected behavior
No error.
Actual behavior
Error in function call (see below).
Terminal Output Screenshot(s)
Additional context
This configuration worked fine with old version v3.2.0.
When patching the module's
main.tf
like this ...... it works correctly. I would submit a PR, but I don't understand the logic / intention well enough to be certain that this is a proper fix for all valid configuration options.
The text was updated successfully, but these errors were encountered: