This message was deleted.

sparse-intern-71089

05/07/2020, 5:55 PM

This message was deleted.

gentle-diamond-70147

05/07/2020, 9:46 PM

I've not seen this error before. What steps did you do prior to hitting this?

abundant-airplane-93796

05/08/2020, 12:53 AM

hard to put my finger on - which is terrible I know. I had just upgraded the

@pulumi/aws

module to 2.3.0 from 2.2.0 -but I'm not convinced that's it. certainly rolling it back hasn't fixed anything

abundant-airplane-93796

05/08/2020, 12:55 AM

I was in the middle of reorganizing my repository - moving some resources around, but without renaming anything, and suddenly started hitting this error.

abundant-airplane-93796

05/08/2020, 12:56 AM

i've tried completely removing the s3 bucket in question from state and 'importing' it, but I get the same error

gentle-diamond-70147

05/08/2020, 1:14 AM

If you're able to reproduce this consistently, would you mind opening an issue at https://github.com/pulumi/pulumi/issues/new with the code that reproduces it?

abundant-airplane-93796

05/08/2020, 1:22 AM

yup - it's something about the current state of the bucket. with a fresh pure new project I can 'get' the bucket, but attempting to import it to take full control gives me the error again

abundant-airplane-93796

05/08/2020, 1:29 AM

https://github.com/pulumi/pulumi/issues/4592

gentle-diamond-70147

05/08/2020, 1:33 AM

Thanks

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.