famous-ambulance-44173
05/08/2025, 8:58 PMsubnets:
- name: ext-az1
...
- name: ext-az2
...
attachments:
- name: tgw-attachment
# some parameters
- name: cwan-attachment
# some parameters
routeTables:
- name: private
routes:
- destination: 0.0.0.0/0
nextHop: igw
- destination: ::/0
nextHop: igw
- destination: 10.0.0.0/8
nextHop: tgw@tgw-attachment # or cwan@cwan-attachment
- destination: subnet@ext-az1.ipv4
nextHop: vpce-123456
- destination: subnet@ext-az1.ipv6
nextHop: vpce-123456
- destination: 10.1.0.0/24
nextHop: pcx@tag:Name=MyPeering,Environment=Prod
- destination: 10.2.0.0/24
nextHop: pcx@ssm:/my/peering/id
what do you think about the syntax? how would you improve it / make clearer for the user?quick-house-41860
05/09/2025, 8:43 AMfamous-ambulance-44173
05/09/2025, 9:39 AMquick-house-41860
05/12/2025, 6:38 AMnextHop
property could have typed inputs for the different things you can pass in.
E.g.
nextHop:
igw:
id: your-igw-id # reference by ID
res: igw # pass the actual resources
tags: # allow selecting it by tags
...
ssm: param-name # SSM param
On the other hand, it would also be fine to just accept IDs in my mind and let users look up the IDs themselves via functions if they're not defined in the same stack 🤔famous-ambulance-44173
05/12/2025, 7:33 AM{{resolve:ssm:/my-peering/id}}
in pulumi yaml, is there a way to do such lookup (e.g. ssm) and store it in the variable to be later used in component args?quick-house-41860
05/12/2025, 8:24 AMfamous-ambulance-44173
05/13/2025, 7:34 PM