-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
Terraform aws - not able to output vpc main_route_table_id #4398
Comments
Hi @worldspawn. Thanks for reporting this - your configuration looks correct as far as I can see, so this looks like a bug. Could you post the resource definitions for your VPC and routing table as well, and I'll try to reproduce/fix? |
Here it is:
Note i'm not defining a route table, i'm expecting it to give me the name of the default route table created when i create the vpc. |
Hi @worldspawn - just dug into this and verified the code is correct. That's when I noticed the cause - your I'll look into whether we can provide a better error message for this, but in the meantime that should get you the proper behavior. |
Also lists out invalid keys in errmsg when they are present Closes #4398
Also lists out invalid keys in errmsg when they are present Closes #4398
Also lists out invalid keys in errmsg when they are present Closes #4398
Sorry about that :) thanks |
Also lists out invalid keys in errmsg when they are present Closes hashicorp#4398
I'm going to lock this issue 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 similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Hi,
i'm trying to output a newly created vpc's main_route_table_id attribute.
However it always comes out as blank.
As you can see I don't have trouble outputting other values.
I can see it's being set in the tfstate file.
Not sure what I'm doing wrong :'(
(Terraform v0.6.8)
The text was updated successfully, but these errors were encountered: