Skip to content
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

How to handle the multiple databases and its schema related accesses in a redshift cluster using the provider #84

Open
rajasekaranmpomelo opened this issue Sep 27, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@rajasekaranmpomelo
Copy link

When we have two databases are configured in a cluster and with different schema's are created on the databases, How can we grant privileges for different schema's on different databases. In the below example, if the raw schema is in one database and staging schema is on another database and our terraform point the 1st database, does the below second resource can identify the staging schema in 2nd database and assigns the necessary privileges?

resource "redshift_default_privileges" "de_raw_transform" {
group = "transform"
owner = "dataeng"
schema = "raw"
object_type = "table"
privileges = ["select"]
}

resource "redshift_default_privileges" "de_staging_transform" {
group = "transform"
owner = "dataengg"
schema = "staging"
object_type = "table"
privileges = ["select"]
}

@jimmymaise
Copy link

i think we may need to add multiple providers

@winglot winglot added the enhancement New feature or request label Jan 19, 2023
@hazmei
Copy link

hazmei commented Feb 3, 2023

Facing the same issue on our end as well. Unfortunately, adding multiple providers is not an option as our terraform code dynamically create new database and would then add the default privileges in the db.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants