alloydb: add ALLOYDB_IAM_GROUP user type to google_alloydb_user (beta) - #18795
Open
kenkania wants to merge 2 commits into
Open
alloydb: add ALLOYDB_IAM_GROUP user type to google_alloydb_user (beta)#18795kenkania wants to merge 2 commits into
kenkania wants to merge 2 commits into
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
modular-magician
added
the
awaiting-approval
ALLOYDB_IAM_GROUP lets a Google group be added as a database user so its members authenticate via IAM group-based authentication. The value is only present in the v1beta discovery document, so user_type is duplicated with exact_version to keep the GA provider (v1) validating the two existing values, following the same pattern as google_healthcare_fhir_store.version. Adds a beta-only sample pair covering the new user type: a documentation example and a test example built on the shared service networking bootstrap, matching the existing ALLOYDB_IAM_USER samples.
kenkania
force-pushed
the
alloydb-user-iam-group
branch
from
August 26, 2026 13:56
97830f2 to
331a104
Compare
|
Googlers: For automatic test runs see go/terraform-auto-test-runs. @roaks3, 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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes: hashicorp/terraform-provider-google#29050
Adds
ALLOYDB_IAM_GROUPtouser_typeongoogle_alloydb_user, so a Google group can be added as a database user and its members can authenticate with IAM group-based authentication.The value only exists in the AlloyDB v1beta discovery document (v1 lists
ALLOYDB_BUILT_INandALLOYDB_IAM_USERonly), souserTypeis duplicated withexact_versionand the new value is beta-only — the same pattern used forversionongoogle_healthcare_fhir_store. The GA copy can be dropped once v1 picks the value up.Test/doc coverage is a beta-only sample pair mirroring the existing
ALLOYDB_IAM_USERsamples: a documentation example and a test example built on the shared service networking bootstrap. Both enable thealloydb.iam_authenticationandalloydb.iam_group_authenticationinstance flags that group authentication requires.Notes for review:
google_compute_backend_service), the beta-only doc example leaves an emptyExample Usagesection in the GA docs page. Happy to drop the doc sample if you'd rather avoid that.--- PASS: TestAccAlloydbUser_alloydbUserIamGroupTestExample (943.69s)