Wojciech Inglot

Hi, there is no separate resource to manage just the group membership. The best, for now, would be to import an existing group to terraform using the `terraform import` command....

Hi, we have faced the same issues and they were fixed in v1.0.4 of the provider (fixing PR: https://github.com/brainly/terraform-provider-redshift/pull/101). It was caused by not cleaning up resources in the Go...

Hi @yauhen-sobaleu I'm currently lacking the capacity to do the implementation. If you wish to implement it on your own and submit a PR, take a look at the `redshift_grant`...

~~Hi, could you be more specific on what kind of role you had in mind?~~ ~~For cluster connection using assume role, it is supported: https://registry.terraform.io/providers/brainly/redshift/latest/docs#authentication-using-temporary-credentials-in-cross-account-scenario~~ edit: I now see you...

Hi, could you share the provider and terraform version you are using? The warning message refers to "legacy plugin SDK" and according to docs is the SDK v1 while the...

I think you can workaround that and have superusers imported and managed by terraform while having their passwords managed externally. When you do an import of `redshift_user`, it leaves the...

Hi, no, the provider does not require the cluster to be public. It requires that the user of the provider has access to the cluster, whether it is by public...

Hi, thanks for the heads up. I will reach out to our AWS TAM to get the exact date and schedule the necessary work.

Seems like AWS made some changes to Redshift Serverless since last week and more tests are now failing. It has something to do with how case-insensitive identifiers are handled. I...