This message was deleted.

i believe here what is happening is that the ec2 resource allows you to specify some settings, like source_dest_check, in the case where you want a network interface created and attached to the instance. so source_dest_check is a property that will be applied to the automatically created network interface. but if you want to bring your own network interface created elsewhere to the instance, it won't generate a network interface. and that network interface already was created with its own source_dest_check=true/false. so the source_dest_check on the ec2 instance "default" is probably actually null or unset - but in the event you want to automatically create a network interface for it (by not supplying your own) it will default to true only in that case

ok, that sounds logical, but it is still a parameter that can be True or False, and non of them works as soon as it is used in

aws.ec2.Instance(..)

https://www.pulumi.com/docs/reference/pkg/aws/ec2/instance/#source_dest_check_python also this parameter works perfect when used in

aws.ec2.NetworkInterface(source_dest_check=False)

i'm less familiar with how python works, but it look like they are not just using booleans, but wrapping them in this `Optional[pulumi.Input[bool]]`: https://github.com/pulumi/pulumi-aws/blob/master/sdk/python/pulumi_aws/ec2/instance.py#L673

@bumpy-grass-54508 thanks for explaining, I debugged this and this is how it works in Pulumi for

aws.ec2.Instance(..)

parameter

source_dest_check=

is not working (or working automagically) and then when using

aws.ec2.NetworkInterface(source_dest_check=<False or True>)

this parameter will inherit into Instance

source_dest_check=

when not using this parameter...

no problem! yeah i think a lot of them can be

None

and will default to

None

, but then later on depending on other conditions the actual "default" value will come into play