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

I would say the state is not the same as your `tfstate`

Maybe use a `pulumi refresh` if your resource does really exist ?

<@UJQTRBP0E> `refresh` didn’t help. But I guess this has something to do with some of the properties of a UserLoginProfile only done at creation time. Not sure if `import` is applicable for this type of resource. From the docs:
&gt; *pgpKey*: Either a base-64 encoded PGP public key, or a keybase username in the form `keybase:username`. Only applies on resource creation. Drift detection is not possible with this argument.

I solved it by manually removing my console login password on my IAM user, then just creating the `UserLoginProfile` resource. It gave me a new password and I am all set.

<@UK4HNFLCB> would you mind filing an issue for this specific resource? My guess is that the underlying TF provider does not return that property when reading the `UserLoginProfile` state from AWS, and so we see a difference.

We're working on extending the `ignoreChanges` resource option to handle cases like this.

<@U84HBHXS8> It took me a while, but here is the requested issue: <https://github.com/pulumi/pulumi-aws/issues/686>