I'd quite like top-level await, to help deal with the dreaded awsx.ec2.Vpc -> subnets issue.

But that requires target: es2017 and module: esnext.

awsx.ec2.Vpc.fromExistingIds()

gives double-wrapped subnet ids, and there's no way (afaik) to make one of those subnet IDs available to a top-level

export

.

Right now I'm dealing with needing an array of all private subnet IDs, and a single subnet ID, in the same block of code. I've gone back and forth countless times. I can't see how to do it, short of hardcoding a subnet ID in my config file.

I've even resorted to the rather-nasty

declare module '@pulumi/pulumi' {
  export interface OutputInstance<T> {
    promise(withUnknowns?: boolean): Promise<T>;
  }
}

but that introduces all sorts of issues when pulumi.Input is used in the same file, because Outputs start auto-converting themselves to Promises...

I use awsx.Vpc in one of my stacks and there are subnetIds in stack outputs, but maybe our use cases are quite different

not sure what does that mean > if you're starting from a vpcId

could you also export subnetids in the same imported stack?

Right now, I'm getting the

pulumi.Input<pulumi.Input<string>[]>

array of private subnet IDs from the VPC, and I'm passing the

pulumi.Input<string>

as a config parameter to the stack. This makes for the cleanest code, with no duplication. I'd like to improve that, because I could just pick a random subnet ID from that array.. but I haven't been able to find a way to do it.

so here is a simplified output example

vpcs   : {
                eu-central-1: [
                    [0]: {
                        id            : "vpc-xxx"
                        name          : "main"
                        subnetIds       : [
                            [0]: "subnet-xxx"
                            [1]: "subnet-yyy"
                            [2]: "subnet-zzz"
                        ]
                    }
                ]
            }