This message was deleted.

Have you tried passing

ResourceOptions

with

dependsOn

set?

In the resource constructor?

Yes

I haven't - I'm still new to Pulumi, do you have an short example?

You should be able to feed the name through and dependencies will be inferred- for example:

const vpc = new aws.ec2.Vpc(`my-vpc`, { ... });

const subnet = new aws.ec2.Subnet(`my-subnet`, {
    vpcId: vpc.id,
    //... other properties
});

What about situations where the infrastructure doesn't have a natural relationship - like subnet - vpc? In this case the Kinesis stream name is being used to generate the Swagger template, which API Gateway doesn't necessarily need

You can refer to any property on an object and the dependency will be tracked through as far as I’m aware!

oh - that's convenient

ID isn’t special cased in that example

Would the same apply to something like this

const ingestAPI = new aws.apigateway.RestApi(
  "ingest",
  {
    body: streamIAMRole.arn.apply(arn => swaggerSpec(arn, gatewayRequestStream))
  },
  { parent: ingestStream }
);

it shold do

That seems to have worked

dependsOn

(like in Terraform) is a blunt tool that you shouldn’t have to use very often - the only times you need it are when two things truly have no exterior relationship but some internal one - it’s usually indicative of an irritating API design at the provider I’ve found