victorious-sugar-42620
04/09/2021, 6:41 PM[WARN] A duplicate Security Group rule was found on (sg-example). This may be a side effect of a now-fixed Terraform issue causing two security groups with
identical attributes but different source_security_group_ids to overwrite each other in the state.
but the only way I managed to work around this is: Delete conflicting rule -> pulumi up -> Recreate conflicting rule manually. Should I set the sourceSecurityGroupId
?deleteBeforeUpdate
billowy-army-68599
04/09/2021, 6:44 PMvictorious-sugar-42620
04/09/2021, 7:36 PMnew awsx.ec2.SecurityGroup(
'platform-lb-sg',
{
vpc,
ingress: [
{ fromPort: 80, toPort: 80, protocol: 'tcp', cidrBlocks: ['0.0.0.0/0'] },
{ fromPort: 1234, toPort: 1234, protocol: 'tcp', cidrBlocks: ['0.0.0.0/0'] },
{ fromPort: 8000, toPort: 8000, protocol: 'tcp', cidrBlocks: ['0.0.0.0/0'] }
],
egress: [{ fromPort: 0, toPort: 65535, protocol: 'tcp', cidrBlocks: [ '0.0.0.0/0' ] }],
}
)
billowy-army-68599
04/09/2021, 7:54 PMawsx
to me, it should be autonaming to prevent this kind of conflictaws.ec2.SecurityGroup
(not the missing x) does it work?