Create new resource for changed aws_iam_user_ssh_key public_key and encoding

[AMeng]

Fixes #378

Changes proposed in this pull request:

• Create a new aws_iam_user_ssh_key resource when either public_key or encoding changes.

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccAWSUserSSHKey'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./... -v -parallel 20 -run=TestAccAWSUserSSHKey -timeout 120m
?   	github.com/terraform-providers/terraform-provider-aws	[no test files]
=== RUN   TestAccAWSUserSSHKey_basic
=== PAUSE TestAccAWSUserSSHKey_basic
=== RUN   TestAccAWSUserSSHKey_pemEncoding
=== PAUSE TestAccAWSUserSSHKey_pemEncoding
=== CONT  TestAccAWSUserSSHKey_basic
=== CONT  TestAccAWSUserSSHKey_pemEncoding
--- PASS: TestAccAWSUserSSHKey_pemEncoding (13.64s)
--- PASS: TestAccAWSUserSSHKey_basic (15.12s)
PASS

According to the AWS API docs, you cannot edit public_key or encoding. Therefore Terraform should create a new resource.

[bflad]

LGTM, thanks so much @AMeng! 🚀

--- PASS: TestAccAWSUserSSHKey_basic (9.22s)
--- PASS: TestAccAWSUserSSHKey_pemEncoding (9.74s)

[bflad]

This has been released in version 1.51.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

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