adamant-dress-73325
08/20/2019, 3:58 PMpulumi refresh
.
++aws:ec2/instance:Instance: (create-replacement)
<snip>
~ securityGroups: [
+ [0]: "sg-082e7a6e007b182dc"
]
+-aws:ec2/instance:Instance: (replace)
~ securityGroups: [
+ [0]: "sg-082e7a6e007b182dc"
]
limited-rainbow-51650
08/20/2019, 4:16 PMpulumi preview/up
on an existing Pulumi setup?adamant-dress-73325
08/20/2019, 4:17 PMlimited-rainbow-51650
08/20/2019, 4:21 PMpulumi up
?adamant-dress-73325
08/20/2019, 4:23 PMconst blahInstance = new aws.ec2.Instance("blah-qa", {
ami: "ami-blah",
instanceType: aws.ec2.InstanceTypes.T3_XLarge,
subnetId: vpcPrivateSubnetIds[0],
securityGroups: [blahSg.id],
keyName: "blah",
associatePublicIpAddress: false,
tags: {
Name: "blah"
}
});
limited-rainbow-51650
08/20/2019, 4:25 PMwhite-balloon-205
securityGroups
is actually the wrong property to use here - you need to use vpcSecurityGroupIds
if you are working with a VPC (which it looks like you are).
I believe the confusion you are seeing comes from some strange behaviour where in this case your securityGroups
wasn't really being applied in the first place, and so it looks like it's constantly trying to reapply it?
I think there have been some previous conversations on this topic in the channel here - such as https://pulumi-community.slack.com/archives/C84L4E3N1/p1562426255155500.adamant-dress-73325
08/20/2019, 4:44 PMlimited-rainbow-51650
08/20/2019, 7:22 PMbroad-dog-22463
08/20/2019, 7:23 PMadamant-dress-73325
08/20/2019, 7:33 PM