-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add google_alloydb_user resouce w/ support for creating IAM users #14272
Comments
User management appears to be done in PSQL directly per https://cloud.google.com/alloydb/docs/database-users/about#manage-users. We'd need this to be exposed in the API to interact with it in Terraform. It shouldn't break through from the control plane to the data plane of the resource. We'd expect users to use a database management tool instead of an infrastructure management tool to interact with the database, or at least a dedicated provider such as the community one here: https://registry.terraform.io/providers/cyrilgdn/postgresql/latest/docs |
b/280326208 |
Leaving a note here, but anyone looking for a workaround can look at this in the meantime: https://registry.terraform.io/modules/terraform-google-modules/gcloud/google/latest It will let you use the |
I'd like to pick this issue up, did some work on it and will add the PR shortly. |
Thanks folks, really appreciate it! Does anyone know when this will be available on terraform registry? |
Hey Franklin, |
@GauravJain21 Thank you! Im closing this issue given it was already resolved |
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. |
Community Note
Description
Add a new resource that allows creating alloydb users using terraform. We currently have a similar feature for cloudsql resource .
This new provider would make possible creation of IAM users, allowing instances to be created without passing any password.
New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: