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.

Pulumi Community

Once you've imported a resource, you absolutely _should_ remove the import opt.

I understand why *may*. I don't understand why *should*.

What's the disadvantage to leaving it besides a no-op?

It's essentially misleading self-documentation. "import" means "take over from another management tool"; once it's taken over by Pulumi, you're no longer doing that.

Also, if you ever do an `up` that causes a replace, your `id` will change. Your `import` opt will say one id, but the state will say a different one.

That's admittedly not very likely, but it does happen for some resources.

That makes sense to me. I understand the *should*. Thanks.