-
Notifications
You must be signed in to change notification settings - Fork 104
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
expose route table ids #885
base: master
Are you sure you want to change the base?
Conversation
Route table ids can be important for VPCs after they've been created. Exposing the route table ids as outputs allows us to easily support resources like NAT instances (cheaper than NAT Gateways), AWS Transit Gateways and AWS Client VPNs
@danielrbradley am I missing something here? I generated the types locally so trying to understand the failures here |
"publicRouteTableIds": { | ||
"type": "array", | ||
"items": { | ||
"type": "string" | ||
} | ||
}, | ||
"privateRouteTableIds": { | ||
"type": "array", | ||
"items": { | ||
"type": "string" | ||
} | ||
}, | ||
"isolatedRouteTableIds": { | ||
"type": "array", | ||
"items": { | ||
"type": "string" | ||
} | ||
}, |
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.
The schema.json is generated by the schemagen
program. The VPC types are defined using this code here: https://github.com/pulumi/pulumi-awsx/blob/master/schemagen/pkg/gen/ec2.go
Route table ids can be important for VPCs after they've been created.
Exposing the route table ids as outputs allows us to easily support resources like NAT instances (cheaper than NAT Gateways), AWS Transit Gateways and AWS Client VPNs