aws_iam_user_ssh_key status and state issue

[eugenetaranov]

Hello,

aws_iam_user_ssh_key seem to have several closely related issues:

• initial creation does not set status correctly, it sets Active for all keys, ignoring Inactive.
• local state part related to aws_iam_user_ssh_key is wiped off.

Terraform Version

Terraform v0.11.3
+ provider.aws v1.8.0

Affected Resource(s)

• aws_iam_user_ssh_key

Terraform Configuration Files

resource "aws_iam_user" "test" {
  name = "test"
  path = "/"
}

resource "aws_iam_user_ssh_key" "test" {
  username   = "${aws_iam_user.test.name}"
  encoding   = "PEM"
  public_key =<<EOF
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDFcMDIpVtqvnm/rQagtR7oRL4WwvQEKLfu+jzyCw9wF4JZNjiLCVVJiCKEqbxc7Qrl/U0LSqOcoOYsn4YTwYqlS2Kob0Z7V1PShWYSPvvUTu6FWzSmXIbwHMQ6RvBdGL740mIgCwgpqoIeOOxrEDQlWEjCLla15p5NSGphHYg32PV0oodauq6RsTK3owtMWd7oyd30yK16MqNufG91JNHG4M/tpUfdd2gQ5SWoLYcAgPXLUWC01+rntIPNc0ZKm+I53R0VhVZVTE/1+nFmJiVZdp7nIEFdr5AjUUPFp3GWUSt7nDAC8OaF9b/3uCmA4emXLecAjz7YtnlXrEaCsauH
EOF
  status     = "Inactive"
}

Debug Output

1st apply: https://gist.github.com/eugenetaranov/3e10bfc38d966d1d361e4218a15708ea
2nd apply: https://gist.github.com/eugenetaranov/dd8fffb772356a694a02b2d1a7f95b45
3rd apply: https://gist.github.com/eugenetaranov/e3d55911491591faae8a9c9451b71232

Panic Output

None

Expected Behavior

create iam user, attach ssh public key with correct status

Actual Behavior

1st run:

• created iam user, uploaded ssh key with incorrect status (Active)
  2nd run:
• ssh key status was updated (Active->Inactive)
• local state was partially wiped off (aws_iam_user_ssh_key is removed)
• wrong username is queried at https://gist.github.com/eugenetaranov/dd8fffb772356a694a02b2d1a7f95b45#file-gistfile1-txt-L658
  3rd run:
• fails with DuplicateSSHPublicKey error (ssh key already exists in IAM).

Steps to Reproduce

Run terraform apply 3 times.

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[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!