I have a CloudWatch Log Group deployed originally via plumi/aws classic. However, on subsequent stac...

bland-painting-33593

05/03/2024, 6:32 PM

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?

Untitled

enough-garden-22763

05/07/2024, 1:08 PM

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

pulumi refresh

bland-painting-33593

05/07/2024, 6:37 PM

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

enough-garden-22763

05/07/2024, 6:59 PM

AFAIK

pulumi up --refresh

pulumi refresh && pulumi up

bland-painting-33593

05/07/2024, 6:59 PM

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

enough-garden-22763

05/07/2024, 7:00 PM

Could you log an issue with repro into

pulumi/pulumi-aws

? My team will have a look. 🙏

bland-painting-33593

05/07/2024, 7:00 PM

will do. Thanks!

7 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.