aws_iam_user_login_profile Automatically Imports Existing Infrastructure During Resource Creation

[bflad]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Affected Resource(s)

• aws_iam_user_login_profile

Terraform Configuration Files

resource "aws_iam_user_login_profile" "example" {
  user    = "${aws_iam_user.example.name}"
  pgp_key = "..."
}

Expected Behavior

If the IAM User already exists and has an existing Login Profile, Terraform should error during resource creation and require terraform import.

Actual Behavior

Terraform silently assumes management of existing IAM User Login Profile during resource creation.

Steps to Reproduce

1. Create IAM User with Login Profile
2. terraform apply above configuration with no existing state

Important Factoids

Requiring resource import is a general design tenet of Terraform to ensure operators understand existing infrastructure and to deter attempting to manage the same infrastructure in two places.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!