I have a CloudWatch Log Group deployed originally via plumi/aws classic. However, on subsequent stack updates, with nothing having changed, it fails because "The specified log group already exists". What am I doing wrong that's causing the state to mess up?

Could it be that Pulumi state lost the record for this Log Group? Try

pulumi refresh

?

Is there a functional difference between that and up --refresh? Because I use that often, probably too much, honestly, but including for this situation.

AFAIK

pulumi up --refresh

~

pulumi refresh && pulumi up

kk, that's what I thought. So yeah, that isn't helping 😞

Could you log an issue with repro into

pulumi/pulumi-aws

? My team will have a look. 🙏

will do. Thanks!