Hello I m using the aws native provider with Go in two very Pulumi Community #aws

Hello, I’m using the aws-native provider with Go i...

bored-spoon-83710

05/26/2025, 11:37 AM

Hello, I’m using the aws-native provider with Go in two very similar projects, that is, they both use a large amount of shared code, for example to create a VPC. When I do a

pulumi refresh

in each project, I do not get the same result for some resources. For example, in the first project, the refresh wants to add the

ipv6CidrBlockNetworkBorderGroup

attribute on the

ec2:VpcCidrBlock

, whereas it does not want to add it in the second. This resource has been configured exactly the same in both project, without specifying this attribute, though. Do you have any idea what could cause this behaviour? I also get this behaviour for the

ec2:VpcEndpoint

resource and its

resourceConfigurationArn

and

serviceNetworkArn

attributes.

bored-spoon-83710

05/26/2025, 12:02 PM

Also, when I get the resources using

aws cloudcontrol get-resource --type-name AWS::EC2::VPCCidrBlock --identifier 'vpc-cidr-assoc-id|vpc-id'

in both projects, the output is the same (except for IDs and CIDR block, of course, but the other attributes are the same), so I don’t understand why Pulumi sees something different in one of the project.

bored-spoon-83710

05/26/2025, 1:52 PM

OK, I think I understand where this discrepancy comes from: in one workspace’s state, the

outputs.__inputs.plaintext

section contains the

ipv6CidrBlockNetworkBorderGroup

, whereas in the second workspace’s state, the

outputs.__inputs.plaintext

section does not contain the

ipv6CidrBlockNetworkBorderGroup

. However, I don’t understand how I ended up in this situation.

5 Views

Open in Slack

Previous Next