mtesch-um

I've run into the same thing trying to setup a chain of (nearly identical) incoming SES rules where there "after" entry should refer to the previous `aws_ses_receipt_rule`. This is another...

Apologies for the bluntness, but this comes across as a sort of cheap advert for supabase at the expense of pgvector users - an attempt to capture pgvector users into...

Random comments on this: - re @joyanujoy 's comment - postgres 14 support would be nice. - @mmmaia the psycopg2 support is nicer since it's simpler(?) than ORM. - re...

@fraserc182 as a workaround until the fix gets merged you ~can~ should be able to manually run `DROP DATABASE "database-prd";`

Maybe also check for prefix of `sha256`? `CREATE USER` seems to take both, while `ALTER USER` seems to take only `md5`, based on docs, not actual experimentation: https://docs.aws.amazon.com/redshift/latest/dg/r_CREATE_USER.html

i ran into this again, and forgot someone already fixed it! thanks @mikemlg also see https://github.com/brainly/terraform-provider-redshift/pull/96

guys it's all open source here, if you're blocked help fix it 😉 that linked PR has some next steps suggested...

@piyush-daga Yes, it's true that the `.tf` file is incorrect - however this should still not cause the provider to create an inconsistent result - the error message from `terraform`...

@winglot hm, yes, that is strange... i'm using `terraform-redshift-provider` v0.5.0 (also checked v0.5.1 and it still happens) and terraform v1.1.2 on darwin_amd64 ,go looking in `log.out`, with settings ```sh export...

~~Not sure if this helps, but I tried the migrator checker https://www.terraform.io/plugin/sdkv2/guides/v1-upgrade-guide#using-tf-sdk-migrator and got:~~ Edit: nevermind, this is all irrelevant. ``` terraform-provider-redshift % ~/go/bin/tf-sdk-migrator check Checking Go runtime version ......