Added support for auto and deprecated automatic field in google_secret_manager_secret resource

[abheda-crest]

Added support for the auto field and deprecated automatic field in the google_secret_manager_secret resource
fixes hashicorp/terraform-provider-google#10679
fixes hashicorp/terraform-provider-google#9272
fixes hashicorp/terraform-provider-google#14282

If this PR is for Terraform, I acknowledge that I have:

• Searched through the issue tracker for an open issue that this either resolves or contributes to, commented on it to claim it, and written "fixes {url}" or "part of {url}" in this PR description. If there were no relevant open issues, I opened one and commented that I would like to work on it (not necessary for very small changes).
• Ensured that all new fields I added that can be set by a user appear in at least one example (for generated resources) or third_party test (for handwritten resources or update tests).
• Generated Terraform providers, and ran make test and make lint in the generated providers to ensure it passes unit and linter tests.
• Ran relevant acceptance tests using my own Google Cloud project and credentials (If the acceptance tests do not yet pass or you are unable to run them, please let your reviewer know).
• Read Write release notes before writing my release note below.

Release Note Template for Downstream PRs (will be copied)

secretmanager: added `auto` field to `google_secret_manager_secret` resource

secretmanager: deprecated `automatic` field on `google_secret_manager_secret`. Use `auto` instead.

[modular-magician]

Hello! I am a robot. It looks like you are a: Community Contributor Googler Core Contributor. Tests will require approval to run.

@SarahFrench, a repository maintainer, has been assigned to review your changes. If you have not received review feedback within 2 business days, please leave a comment on this PR asking them to take a look.

You can help make sure that review is quick by doing a self-review and by running impacted tests locally.

[abheda-crest]

This PR follows the approach suggested by @slevenick in his comment.

[abheda-crest]

@SarahFrench Could you please start the tests as it is awaiting your approval and review this PR?

[modular-magician]

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

Terraform GA: Diff ( 26 files changed, 438 insertions(+), 50 deletions(-))
Terraform Beta: Diff ( 30 files changed, 443 insertions(+), 55 deletions(-))
TF Conversion: Diff ( 1 file changed, 63 insertions(+), 5 deletions(-))
TF OiCS: Diff ( 16 files changed, 134 insertions(+), 12 deletions(-))

[modular-magician]

Tests analytics

Total tests: 3010
Passed tests 2711
Skipped tests: 296
Affected tests: 3

Action taken

Found 3 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests

TestAccDataSourceGoogleServiceAccountJwt|TestAccSecretManagerSecret_automaticCmekUpdate|TestAccSecretManagerSecret_secretWithAutomaticCmekExample

Get to know how VCR tests work

[modular-magician]

$\textcolor{green}{\textsf{Tests passed during RECORDING mode:}}$
TestAccDataSourceGoogleServiceAccountJwt[Debug log]
TestAccSecretManagerSecret_automaticCmekUpdate[Debug log]
TestAccSecretManagerSecret_secretWithAutomaticCmekExample[Debug log]

Rerun these tests in REPLAYING mode to catch issues

$\textcolor{green}{\textsf{No issues found for passed tests after REPLAYING rerun.}}$

---

$\textcolor{green}{\textsf{All tests passed!}}$
View the build log or the debug log for each test

[abheda-crest]

@SarahFrench Could you please review this PR?

[SarahFrench]

👋 I've caught up on context needed to review this PR. As this PR is trying to avoid breaking changes, could you please update this handwritten acceptance test to show that an old config that still uses automatic = true still works as expected?

[abheda-crest]

👋 I've caught up on context needed to review this PR. As this PR is trying to avoid breaking changes, could you please update this handwritten acceptance test to show that an old config that still uses automatic = true still works as expected?

I've added a test case that covers the automatic = true. Just to clarify, while importing the secret resources having the old field automatic = true, the imported resource will have the new field auto as an empty object instead and the automatic field will be false. Hence, I've kept replication.0.auto and replication.0.automatic in ImportStateVerifyIgnore.

[abheda-crest]

@SarahFrench Could you please start the tests and review the changes?

[modular-magician]

Hi there, I'm the Modular magician. I've detected the following information about your changes:

Diff report

Your PR generated some diffs in downstreams - here they are.

Terraform GA: Diff ( 26 files changed, 479 insertions(+), 50 deletions(-))
Terraform Beta: Diff ( 30 files changed, 484 insertions(+), 55 deletions(-))
TF Conversion: Diff ( 1 file changed, 63 insertions(+), 5 deletions(-))
TF OiCS: Diff ( 16 files changed, 134 insertions(+), 12 deletions(-))

[modular-magician]

Tests analytics

Total tests: 3020
Passed tests 2722
Skipped tests: 297
Affected tests: 1

Action taken

Found 1 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests

TestAccSecretManagerSecret_automaticCmekUpdate

Get to know how VCR tests work

[modular-magician]

$\textcolor{green}{\textsf{Tests passed during RECORDING mode:}}$
TestAccSecretManagerSecret_automaticCmekUpdate[Debug log]

Rerun these tests in REPLAYING mode to catch issues

$\textcolor{green}{\textsf{No issues found for passed tests after REPLAYING rerun.}}$

---

$\textcolor{green}{\textsf{All tests passed!}}$
View the build log or the debug log for each test