[#19212] Fix secretsmanager_secret_version update

[syndbg]

Fixes the AWS SecretsManager API call failing when there's a drift
between the Terraform state and SecretsManager "state".

The drift is caused by someone/something updating outside of Terraform the given resource.
E.g AWS SecretsManager CLI or AWS SecretsManager Web UI/Console

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Closes #19212.

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccAwsSecretsManagerSecretVersion_VersionStages_external_update'
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./aws -v -count 1 -parallel 20 -run=TestAccAwsSecretsManagerSecretVersion_VersionStages_external_update -timeout 180m
=== RUN   TestAccAwsSecretsManagerSecretVersion_VersionStages_external_update
=== PAUSE TestAccAwsSecretsManagerSecretVersion_VersionStages_external_update
=== CONT  TestAccAwsSecretsManagerSecretVersion_VersionStages_external_update
--- PASS: TestAccAwsSecretsManagerSecretVersion_VersionStages_external_update (61.19s)
PASS
ok      github.com/terraform-providers/terraform-provider-aws/aws       61.246s
...

[github-actions]

Welcome @syndbg 👋

It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTING guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.

Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.

Thanks again, and welcome to the community! 😃

[syndbg]

Any chance you can take a look at this? @ewbankkit @bill-rich 👀

[syndbg]

Is there anything missing/done wrong in the PR?

We (https://github.com/sumup) kinda need this fix.

[zhelding]

Pull request #21306 has significantly refactored the AWS Provider codebase. As a result, most PRs opened prior to the refactor now have merge conflicts that must be resolved before proceeding.

Specifically, PR #21306 relocated the code for all AWS resources and data sources from a single aws directory to a large number of separate directories in internal/service, each corresponding to a particular AWS service. This separation of code has also allowed for us to simplify the names of underlying functions -- while still avoiding namespace collisions.

We recognize that many pull requests have been open for some time without yet being addressed by our maintainers. Therefore, we want to make it clear that resolving these conflicts in no way affects the prioritization of a particular pull request. Once a pull request has been prioritized for review, the necessary changes will be made by a maintainer -- either directly or in collaboration with the pull request author.

For a more complete description of this refactor, including examples of how old filepaths and function names correspond to their new counterparts: please refer to issue #20000.

For a quick guide on how to amend your pull request to resolve the merge conflicts resulting from this refactor and bring it in line with our new code patterns: please refer to our Service Package Refactor Pull Request Guide.

[X-Guardian]

@syndbg, are you able to resolve the conflicts on this PR, as this issue still exists.

[ewbankkit]

LGTM 🚀.

% make testacc TESTARGS='-run=TestAccSecretsManagerSecretVersion_' PKG=secretsmanager ACCTEST_PARALLELISM=3
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/secretsmanager/... -v -count 1 -parallel 3  -run=TestAccSecretsManagerSecretVersion_ -timeout 360m
=== RUN   TestAccSecretsManagerSecretVersion_basicString
=== PAUSE TestAccSecretsManagerSecretVersion_basicString
=== RUN   TestAccSecretsManagerSecretVersion_base64Binary
=== PAUSE TestAccSecretsManagerSecretVersion_base64Binary
=== RUN   TestAccSecretsManagerSecretVersion_versionStages
=== PAUSE TestAccSecretsManagerSecretVersion_versionStages
=== RUN   TestAccSecretsManagerSecretVersion_versionStagesExternalUpdate
=== PAUSE TestAccSecretsManagerSecretVersion_versionStagesExternalUpdate
=== RUN   TestAccSecretsManagerSecretVersion_disappears
=== PAUSE TestAccSecretsManagerSecretVersion_disappears
=== RUN   TestAccSecretsManagerSecretVersion_Disappears_secret
=== PAUSE TestAccSecretsManagerSecretVersion_Disappears_secret
=== RUN   TestAccSecretsManagerSecretVersion_multipleVersions
=== PAUSE TestAccSecretsManagerSecretVersion_multipleVersions
=== CONT  TestAccSecretsManagerSecretVersion_basicString
=== CONT  TestAccSecretsManagerSecretVersion_disappears
=== CONT  TestAccSecretsManagerSecretVersion_versionStages
--- PASS: TestAccSecretsManagerSecretVersion_disappears (19.03s)
=== CONT  TestAccSecretsManagerSecretVersion_multipleVersions
--- PASS: TestAccSecretsManagerSecretVersion_basicString (22.62s)
=== CONT  TestAccSecretsManagerSecretVersion_base64Binary
--- PASS: TestAccSecretsManagerSecretVersion_multipleVersions (20.49s)
=== CONT  TestAccSecretsManagerSecretVersion_Disappears_secret
--- PASS: TestAccSecretsManagerSecretVersion_base64Binary (21.78s)
=== CONT  TestAccSecretsManagerSecretVersion_versionStagesExternalUpdate
--- PASS: TestAccSecretsManagerSecretVersion_versionStages (49.04s)
--- PASS: TestAccSecretsManagerSecretVersion_Disappears_secret (18.05s)
--- PASS: TestAccSecretsManagerSecretVersion_versionStagesExternalUpdate (27.47s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/secretsmanager	81.236s

[ewbankkit]

@syndbg Thanks for the contribution 🎉 👏.

[github-actions]

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

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.