Add support for regional secret resource google_secret_manager_regional_secret
#8170
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add support for new regional secret resource
google_secret_manager_regional_secret
. I have also defined theiam_policy
field in the RegionalSecret.yaml file to include the IAM resources and IAM datasources as well.More info about regional secrets: https://cloud.google.com/secret-manager/docs/regional-secrets-overview
Notes:
RegionalSecret.yaml
file, the versionAliases field is commented and the respective test cases covered in theresource_secret_manager_regional_secret_test.go.erb
file are also commented because this field depends on creating regional_secret_version_resource. We intend to uncomment once this PR is merged and dependent tests can pass.ResourceSecret.yaml
file will be updated later.Release Note Template for Downstream PRs (will be copied)
Derived from GoogleCloudPlatform/magic-modules#11678