That said, it’s also completely hallucinating a solution to my current question 🙂 maybe I’ll ask that here too: I’m trying to extract the CIDR blocks for just the private subnets in a VPC (created with

awsx.ec2.Vpc

). The

vpc

object exposes

privateSubnetIds

and

subnets

- I was hoping to combine the two using code like the below. However, it complains that

subnet.id

is

Output<string>

and

includes()

of course expects a

string

. Is this something which is possible? The alternative is to re-query the subnets using

aws.ec2.getSubnet

, but that feels kind of iffy/unnecessary, when the subnets are already available on the

vpc

object.

export const privateSubnetCidrs = pulumi
  .all([vpc.subnets, vpc.privateSubnetIds])
  .apply(([subnets, privateSubnetIds]) => {
    return subnets
      .filter(subnet => privateSubnetIds.includes(subnet.id))
      .map(subnet => subnet.cidrBlock);
  });

You can add subnetIds into your all/apply guards. However, you don't need to. The awsx VPC does indeed have a privateSubnets property, you don't need to filter subnets by id. https://www.pulumi.com/registry/packages/awsx/api-docs/ec2/vpc/#privatesubnetids_nodejs

This maybe sort of seems to work (untested, but types are happy):

export const privateSubnetCidrs = pulumi
  .all([vpc.subnets, vpc.privateSubnetIds])
  .apply(([subnets, privateSubnetIds]) => {
    const cidrBlocks: string[] = [];
    for (const subnet of subnets) {
      pulumi
        .all([subnet.id, subnet.cidrBlock])
        .apply(([subnetId, cidrBlock]) => {
          if (privateSubnetIds.includes(subnetId) && cidrBlock) {
            cidrBlocks.push(cidrBlock);
          }
        });
    }
    return cidrBlocks;
  });

It's massive overkill.

@little-cartoon-10569 it has

privateSubnetIds

, but NOT

privateSubnets

It does. I use it. Have a look at the link I sent.

I want you to be right, but I don’t think you are 🙃 https://github.com/pulumi/pulumi-awsx/blob/master/awsx/ec2/vpc.ts

I found it. It's not in AWSX, only AWSXclassic (which is what I use: it's in the same library, in the awsx.classic namespace). You can use that it you prefer.

Ahhh gotcha, I wonder if there are other meaningful differences between those two

Yes, there are a few. I'm surprised it's that hard to get CIDRs (or indeed, subnets) out of the code. I'll have a quick hunt through examples...

All good, thanks for taking a look anyway! I think the code I ended up with is… readable, if verbose

is there a easy way to extract the private subnet ids from the awsx.ec2.Vpc ? I need to add additional route to the routetable for the private subnets

You cannot convert it to a string[] at the top level. Output<string[]> means a string[] that will be available in the indefinite future, not now. It's simply not available yet. Instead, you can apply() the Output. The string[] is made available as a parameter to your callback in apply().