proud-tiger-5743
09/24/2018, 10:53 PMname
of the previous one, how can I ensure that infrastructure A exists before Infrastructure B is created?full-dress-10026
09/24/2018, 10:57 PMResourceOptions
with dependsOn
set?proud-tiger-5743
09/24/2018, 10:58 PMfull-dress-10026
09/24/2018, 10:58 PMproud-tiger-5743
09/24/2018, 11:00 PMstocky-spoon-28903
09/24/2018, 11:05 PMconst vpc = new aws.ec2.Vpc(`my-vpc`, { ... });
const subnet = new aws.ec2.Subnet(`my-subnet`, {
vpcId: vpc.id,
//... other properties
});
proud-tiger-5743
09/24/2018, 11:08 PMprevious
name of the streamstocky-spoon-28903
09/24/2018, 11:20 PMproud-tiger-5743
09/24/2018, 11:20 PMstocky-spoon-28903
09/24/2018, 11:20 PMproud-tiger-5743
09/24/2018, 11:21 PMconst ingestAPI = new aws.apigateway.RestApi(
"ingest",
{
body: streamIAMRole.arn.apply(arn => swaggerSpec(arn, gatewayRequestStream))
},
{ parent: ingestStream }
);
stocky-spoon-28903
09/24/2018, 11:21 PMproud-tiger-5743
09/24/2018, 11:26 PMstocky-spoon-28903
09/24/2018, 11:27 PMdependsOn
(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