Fixing bootstrapping issues with migrations.

[siennathesane]

What kind of change does this PR introduce?

Big fix for #1729, #1848, #1983, and #2040 with an additional type fix.

What is the current behavior?

The auth service cannot be deployed in a net new environment on PostgreSQL 17.

What is the new behavior?

The service is running properly with PostgreSQL 17 in a cleanroom environment.

Additional context

Here is a redacted version of the terraform I used to deploy it with. I used my own container build with these fixes, ghcr.io/siennathesane/auth:v2.175.0, that you can use to verify the fix is valid, if you want.

locals {
f2-auth-db-namespace="auth"
}
resource"kubernetes_service_account""f2-auth" {
metadata {
name="f2-auth"namespace=var.namespace
}
}
resource"kubernetes_manifest""f2-auth-db" {
manifest={
"apiVersion"="postgresql.cnpg.io/v1""kind"="Database""metadata"= {
"name"="f2-auth-db""namespace"= var.namespace
}
"spec"= {
"cluster"= {
"name"= kubernetes_manifest.f2-cluster.object.metadata.name
}
"allowConnections"=true"name"= local.f2-auth-db-namespace
"owner"= kubernetes_secret_v1.f2-auth-db.data.username
"schemas"= [{
"name"= local.f2-auth-db-namespace
"owner"= kubernetes_secret_v1.f2-auth-db.data.username
}]
}
}
}
resource"kubernetes_config_map_v1""f2-auth-initdb" {
metadata {
name="sql-commands"namespace=var.namespace
}
data={
"script.sql"=<<-EOT ALTER USER ${kubernetes_secret_v1.f2-auth-db.data.username} WITH LOGIN CREATEROLE CREATEDB REPLICATION BYPASSRLS; GRANT ${kubernetes_secret_v1.f2-auth-db.data.username} TO postgres; CREATE SCHEMA IF NOT EXISTS ${local.f2-auth-db-namespace} AUTHORIZATION ${kubernetes_secret_v1.f2-auth-db.data.username}; GRANT CREATE ON DATABASE postgres TO ${kubernetes_secret_v1.f2-auth-db.data.username}; ALTER USER ${kubernetes_secret_v1.f2-auth-db.data.username} SET search_path = '${local.f2-auth-db-namespace}'; EOT
}
}
resource"kubernetes_secret_v1""f2-auth-db" {
metadata {
name="auth-db"namespace=var.namespacelabels={
"cnpg.io/reload"="true"
}
}
data={
username ="[REDACTED]"
password = random_password.f2-auth-db-password.result
database ="auth"
}
type="kubernetes.io/basic-auth"
}
resource"kubernetes_secret_v1""f2-auth-jwt" {
metadata {
name="auth-jwt"namespace=var.namespace
}
data={
anonKey ="[REDACTED]"
secret ="[REDACTED]"
serviceKey ="[REDACTED]"
}
type="Opaque"
}
resource"random_password""f2-auth-db-password" {
length=16special=false
}
resource"kubernetes_deployment_v1""f2-auth" {
depends_on=[kubernetes_manifest.f2-auth-db]
timeouts {
create="2m"
}
metadata {
name="f2auth"labels={
"f2.pub/app"="auth-${var.environment}"
}
namespace=var.namespace
}
spec {
replicas=1selector {
match_labels={
"f2.pub/app"="auth-${var.environment}"
}
}
template {
metadata {
labels={
"f2.pub/app"="auth-${var.environment}"
}
}
spec {
image_pull_secrets { name=var.ghcr-pull-secret-name }
init_container {
name="init-db"image="postgres:17-alpine"command=["psql", "-f", "/sql/script.sql"]
env {
name="PGHOST"value="${kubernetes_manifest.f2-cluster.object.metadata.name}-rw"
}
env {
name="PGPORT"value="5432"
}
env {
name="PGDATABASE"value=kubernetes_secret_v1.f2-auth-db.data.database
}
env {
name="PGUSER"value=kubernetes_secret_v1.f2-auth-db.data.username
}
env {
name="PGPASSWORD"value=kubernetes_secret_v1.f2-auth-db.data.password
}
volume_mount {
name="sql-volume"mount_path="/sql"
}
}
volume {
name="sql-volume"config_map {
name=kubernetes_config_map_v1.f2-auth-initdb.metadata[0].name
}
}
container {
image="ghcr.io/siennathesane/auth:${var.goauth-version}"image_pull_policy="Always"name="auth"resources {
limits={
cpu ="0.5"
memory ="512Mi"
}
requests={
cpu ="250m"
memory ="50Mi"
}
}
port {
name="http"container_port=9999protocol="TCP"
}
env {
name="GOTRUE_DB_DRIVER"value="postgres"
}
env {
name="DB_NAMESPACE"value="auth"
}
env {
name="DATABASE_URL"value="postgres://${kubernetes_secret_v1.f2-auth-db.data.username}:[REDACTED]@${kubernetes_manifest.f2-cluster.object.metadata.name}-rw:5432/${kubernetes_secret_v1.f2-auth-db.data.database}"
}
env {
name="GOTRUE_JWT_SECRET"value_from {
secret_key_ref {
name="auth-jwt"key="secret"
}
}
}
env {
name="API_EXTERNAL_URL"value="http://[REDACTED]"
}
env {
name="GOTRUE_SITE_URL"value="http://[REDACTED]"
}
env {
name="GOTRUE_API_HOST"value="0.0.0.0"
}
env {
name="PORT"value="9999"
}
}
}
}
}
}

Closes#1729
Closes#1848
Closes#1983
Closes#2040

[siennathesane]

@kangmingtay can you please review this so it can get merged? It's an ongoing issue for a lot for people.

[willnode]

+1

[siennathesane]

I guess supabase really doesn't care about OSS contributions

[cstockton]

Hi @siennathesane@willnode — First I wanted to say we do care and appreciate both your contributions very much. Sorry for the delay on these reviews, I'll bring this up with the team to brainstorm how to improve.

I reviewed all the migration related PRs/issues and wanted to ensure the original contributions from @willnode (#1983, #2040) and the (id::text = user_id::text fix) in #2047 were preserved correctly so I was going to create a new PR with everything cherry picked.

I mistakingly force pushed to the wrong upstream after cherry picking 1983 & 2040, which lost the ID change. To try to fix this I reintroduced your id migration fix as a separate commit using your previous git log message and commit. However, I noticed that GitHub now marks your commit as unverified since it didn’t come from your GPG key, and I want to respect your authorship standards.

If you would like to force push a signed commit and tag me I'll make sure this gets reviewed. Sorry for the trouble but looking forward to getting these migration pulls and issues closed out.

[willnode]

You can force push again to the original commit 25697bc which should restore this PR

[cstockton]

@willnode Since you are okay with losing authorship I've restored the prior commit. Thank you!

[cstockton]

👍

[siennathesane]

@willnode when I wrote this, I had included your fixes plus my own. Didn't mean to erase your contribution at all! 🫶

[willnode]

LGTM

[coveralls]

Pull Request Test Coverage Report for Build 20113075029

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 68.527%

---

Totals
Change from base Build 20080137533:	0.0%
Covered Lines:	14682
Relevant Lines:	21425

---

💛 - Coveralls

[bartcode]

Could this be merged still, @willnode ? There hasn't been an update in two months even though everything is good to go. A lot of people must be waiting for this issue to be fixed.

@siennathesane , thank you for this fix! I ran into this exact same issue and luckily found your open PR.

[cstockton]

Sorry for the delay here, I'll merge this after tests run.

[siennathesane]

What kind of change does this PR introduce?

Big fix for #1729, #1848, #1983, and #2040 with an additional type fix.

What is the current behavior?

The auth service cannot be deployed in a net new environment on PostgreSQL 17.

What is the new behavior?

The service is running properly with PostgreSQL 17 in a cleanroom environment.

Additional context

Here is a redacted version of the terraform I used to deploy it with. I used my own container build with these fixes, ghcr.io/siennathesane/auth:v2.175.0, that you can use to verify the fix is valid, if you want.

locals {
f2-auth-db-namespace="auth"
}
resource"kubernetes_service_account""f2-auth" {
metadata {
name="f2-auth"namespace=var.namespace
}
}
resource"kubernetes_manifest""f2-auth-db" {
manifest={
"apiVersion"="postgresql.cnpg.io/v1""kind"="Database""metadata"= {
"name"="f2-auth-db""namespace"= var.namespace
}
"spec"= {
"cluster"= {
"name"= kubernetes_manifest.f2-cluster.object.metadata.name
}
"allowConnections"=true"name"= local.f2-auth-db-namespace
"owner"= kubernetes_secret_v1.f2-auth-db.data.username
"schemas"= [{
"name"= local.f2-auth-db-namespace
"owner"= kubernetes_secret_v1.f2-auth-db.data.username
}]
}
}
}
resource"kubernetes_config_map_v1""f2-auth-initdb" {
metadata {
name="sql-commands"namespace=var.namespace
}
data={
"script.sql"=<<-EOT ALTER USER ${kubernetes_secret_v1.f2-auth-db.data.username} WITH LOGIN CREATEROLE CREATEDB REPLICATION BYPASSRLS; GRANT ${kubernetes_secret_v1.f2-auth-db.data.username} TO postgres; CREATE SCHEMA IF NOT EXISTS ${local.f2-auth-db-namespace} AUTHORIZATION ${kubernetes_secret_v1.f2-auth-db.data.username}; GRANT CREATE ON DATABASE postgres TO ${kubernetes_secret_v1.f2-auth-db.data.username}; ALTER USER ${kubernetes_secret_v1.f2-auth-db.data.username} SET search_path = '${local.f2-auth-db-namespace}'; EOT
}
}
resource"kubernetes_secret_v1""f2-auth-db" {
metadata {
name="auth-db"namespace=var.namespacelabels={
"cnpg.io/reload"="true"
}
}
data={
username ="[REDACTED]"
password = random_password.f2-auth-db-password.result
database ="auth"
}
type="kubernetes.io/basic-auth"
}
resource"kubernetes_secret_v1""f2-auth-jwt" {
metadata {
name="auth-jwt"namespace=var.namespace
}
data={
anonKey ="[REDACTED]"
secret ="[REDACTED]"
serviceKey ="[REDACTED]"
}
type="Opaque"
}
resource"random_password""f2-auth-db-password" {
length=16special=false
}
resource"kubernetes_deployment_v1""f2-auth" {
depends_on=[kubernetes_manifest.f2-auth-db]
timeouts {
create="2m"
}
metadata {
name="f2auth"labels={
"f2.pub/app"="auth-${var.environment}"
}
namespace=var.namespace
}
spec {
replicas=1selector {
match_labels={
"f2.pub/app"="auth-${var.environment}"
}
}
template {
metadata {
labels={
"f2.pub/app"="auth-${var.environment}"
}
}
spec {
image_pull_secrets { name=var.ghcr-pull-secret-name }
init_container {
name="init-db"image="postgres:17-alpine"command=["psql", "-f", "/sql/script.sql"]
env {
name="PGHOST"value="${kubernetes_manifest.f2-cluster.object.metadata.name}-rw"
}
env {
name="PGPORT"value="5432"
}
env {
name="PGDATABASE"value=kubernetes_secret_v1.f2-auth-db.data.database
}
env {
name="PGUSER"value=kubernetes_secret_v1.f2-auth-db.data.username
}
env {
name="PGPASSWORD"value=kubernetes_secret_v1.f2-auth-db.data.password
}
volume_mount {
name="sql-volume"mount_path="/sql"
}
}
volume {
name="sql-volume"config_map {
name=kubernetes_config_map_v1.f2-auth-initdb.metadata[0].name
}
}
container {
image="ghcr.io/siennathesane/auth:${var.goauth-version}"image_pull_policy="Always"name="auth"resources {
limits={
cpu ="0.5"
memory ="512Mi"
}
requests={
cpu ="250m"
memory ="50Mi"
}
}
port {
name="http"container_port=9999protocol="TCP"
}
env {
name="GOTRUE_DB_DRIVER"value="postgres"
}
env {
name="DB_NAMESPACE"value="auth"
}
env {
name="DATABASE_URL"value="postgres://${kubernetes_secret_v1.f2-auth-db.data.username}:[REDACTED]@${kubernetes_manifest.f2-cluster.object.metadata.name}-rw:5432/${kubernetes_secret_v1.f2-auth-db.data.database}"
}
env {
name="GOTRUE_JWT_SECRET"value_from {
secret_key_ref {
name="auth-jwt"key="secret"
}
}
}
env {
name="API_EXTERNAL_URL"value="http://[REDACTED]"
}
env {
name="GOTRUE_SITE_URL"value="http://[REDACTED]"
}
env {
name="GOTRUE_API_HOST"value="0.0.0.0"
}
env {
name="PORT"value="9999"
}
}
}
}
}
}

Closes#1729
Closes#1848
Closes#1983
Closes#2040

[siennathesane]

@kangmingtay can you please review this so it can get merged? It's an ongoing issue for a lot for people.

[willnode]

+1

[siennathesane]

I guess supabase really doesn't care about OSS contributions

[cstockton]

Hi @siennathesane@willnode — First I wanted to say we do care and appreciate both your contributions very much. Sorry for the delay on these reviews, I'll bring this up with the team to brainstorm how to improve.

I reviewed all the migration related PRs/issues and wanted to ensure the original contributions from @willnode (#1983, #2040) and the (id::text = user_id::text fix) in #2047 were preserved correctly so I was going to create a new PR with everything cherry picked.

I mistakingly force pushed to the wrong upstream after cherry picking 1983 & 2040, which lost the ID change. To try to fix this I reintroduced your id migration fix as a separate commit using your previous git log message and commit. However, I noticed that GitHub now marks your commit as unverified since it didn’t come from your GPG key, and I want to respect your authorship standards.

If you would like to force push a signed commit and tag me I'll make sure this gets reviewed. Sorry for the trouble but looking forward to getting these migration pulls and issues closed out.

[willnode]

You can force push again to the original commit 25697bc which should restore this PR

[cstockton]

@willnode Since you are okay with losing authorship I've restored the prior commit. Thank you!

[cstockton]

👍

[siennathesane]

@willnode when I wrote this, I had included your fixes plus my own. Didn't mean to erase your contribution at all! 🫶

[willnode]

LGTM

[coveralls]

Pull Request Test Coverage Report for Build 20113075029

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 68.527%

---

Totals
Change from base Build 20080137533:	0.0%
Covered Lines:	14682
Relevant Lines:	21425

---

💛 - Coveralls

[bartcode]

Could this be merged still, @willnode ? There hasn't been an update in two months even though everything is good to go. A lot of people must be waiting for this issue to be fixed.

@siennathesane , thank you for this fix! I ran into this exact same issue and luckily found your open PR.

[cstockton]

Sorry for the delay here, I'll merge this after tests run.

[siennathesane]

What kind of change does this PR introduce?

Big fix for #1729, #1848, #1983, and #2040 with an additional type fix.

What is the current behavior?

The auth service cannot be deployed in a net new environment on PostgreSQL 17.

What is the new behavior?

The service is running properly with PostgreSQL 17 in a cleanroom environment.

Additional context

Here is a redacted version of the terraform I used to deploy it with. I used my own container build with these fixes, ghcr.io/siennathesane/auth:v2.175.0, that you can use to verify the fix is valid, if you want.

locals {
f2-auth-db-namespace="auth"
}
resource"kubernetes_service_account""f2-auth" {
metadata {
name="f2-auth"namespace=var.namespace
}
}
resource"kubernetes_manifest""f2-auth-db" {
manifest={
"apiVersion"="postgresql.cnpg.io/v1""kind"="Database""metadata"= {
"name"="f2-auth-db""namespace"= var.namespace
}
"spec"= {
"cluster"= {
"name"= kubernetes_manifest.f2-cluster.object.metadata.name
}
"allowConnections"=true"name"= local.f2-auth-db-namespace
"owner"= kubernetes_secret_v1.f2-auth-db.data.username
"schemas"= [{
"name"= local.f2-auth-db-namespace
"owner"= kubernetes_secret_v1.f2-auth-db.data.username
}]
}
}
}
resource"kubernetes_config_map_v1""f2-auth-initdb" {
metadata {
name="sql-commands"namespace=var.namespace
}
data={
"script.sql"=<<-EOT ALTER USER ${kubernetes_secret_v1.f2-auth-db.data.username} WITH LOGIN CREATEROLE CREATEDB REPLICATION BYPASSRLS; GRANT ${kubernetes_secret_v1.f2-auth-db.data.username} TO postgres; CREATE SCHEMA IF NOT EXISTS ${local.f2-auth-db-namespace} AUTHORIZATION ${kubernetes_secret_v1.f2-auth-db.data.username}; GRANT CREATE ON DATABASE postgres TO ${kubernetes_secret_v1.f2-auth-db.data.username}; ALTER USER ${kubernetes_secret_v1.f2-auth-db.data.username} SET search_path = '${local.f2-auth-db-namespace}'; EOT
}
}
resource"kubernetes_secret_v1""f2-auth-db" {
metadata {
name="auth-db"namespace=var.namespacelabels={
"cnpg.io/reload"="true"
}
}
data={
username ="[REDACTED]"
password = random_password.f2-auth-db-password.result
database ="auth"
}
type="kubernetes.io/basic-auth"
}
resource"kubernetes_secret_v1""f2-auth-jwt" {
metadata {
name="auth-jwt"namespace=var.namespace
}
data={
anonKey ="[REDACTED]"
secret ="[REDACTED]"
serviceKey ="[REDACTED]"
}
type="Opaque"
}
resource"random_password""f2-auth-db-password" {
length=16special=false
}
resource"kubernetes_deployment_v1""f2-auth" {
depends_on=[kubernetes_manifest.f2-auth-db]
timeouts {
create="2m"
}
metadata {
name="f2auth"labels={
"f2.pub/app"="auth-${var.environment}"
}
namespace=var.namespace
}
spec {
replicas=1selector {
match_labels={
"f2.pub/app"="auth-${var.environment}"
}
}
template {
metadata {
labels={
"f2.pub/app"="auth-${var.environment}"
}
}
spec {
image_pull_secrets { name=var.ghcr-pull-secret-name }
init_container {
name="init-db"image="postgres:17-alpine"command=["psql", "-f", "/sql/script.sql"]
env {
name="PGHOST"value="${kubernetes_manifest.f2-cluster.object.metadata.name}-rw"
}
env {
name="PGPORT"value="5432"
}
env {
name="PGDATABASE"value=kubernetes_secret_v1.f2-auth-db.data.database
}
env {
name="PGUSER"value=kubernetes_secret_v1.f2-auth-db.data.username
}
env {
name="PGPASSWORD"value=kubernetes_secret_v1.f2-auth-db.data.password
}
volume_mount {
name="sql-volume"mount_path="/sql"
}
}
volume {
name="sql-volume"config_map {
name=kubernetes_config_map_v1.f2-auth-initdb.metadata[0].name
}
}
container {
image="ghcr.io/siennathesane/auth:${var.goauth-version}"image_pull_policy="Always"name="auth"resources {
limits={
cpu ="0.5"
memory ="512Mi"
}
requests={
cpu ="250m"
memory ="50Mi"
}
}
port {
name="http"container_port=9999protocol="TCP"
}
env {
name="GOTRUE_DB_DRIVER"value="postgres"
}
env {
name="DB_NAMESPACE"value="auth"
}
env {
name="DATABASE_URL"value="postgres://${kubernetes_secret_v1.f2-auth-db.data.username}:[REDACTED]@${kubernetes_manifest.f2-cluster.object.metadata.name}-rw:5432/${kubernetes_secret_v1.f2-auth-db.data.database}"
}
env {
name="GOTRUE_JWT_SECRET"value_from {
secret_key_ref {
name="auth-jwt"key="secret"
}
}
}
env {
name="API_EXTERNAL_URL"value="http://[REDACTED]"
}
env {
name="GOTRUE_SITE_URL"value="http://[REDACTED]"
}
env {
name="GOTRUE_API_HOST"value="0.0.0.0"
}
env {
name="PORT"value="9999"
}
}
}
}
}
}

Closes#1729
Closes#1848
Closes#1983
Closes#2040

[siennathesane]

@kangmingtay can you please review this so it can get merged? It's an ongoing issue for a lot for people.

[willnode]

+1

[siennathesane]

I guess supabase really doesn't care about OSS contributions

[cstockton]

Hi @siennathesane@willnode — First I wanted to say we do care and appreciate both your contributions very much. Sorry for the delay on these reviews, I'll bring this up with the team to brainstorm how to improve.

I reviewed all the migration related PRs/issues and wanted to ensure the original contributions from @willnode (#1983, #2040) and the (id::text = user_id::text fix) in #2047 were preserved correctly so I was going to create a new PR with everything cherry picked.

I mistakingly force pushed to the wrong upstream after cherry picking 1983 & 2040, which lost the ID change. To try to fix this I reintroduced your id migration fix as a separate commit using your previous git log message and commit. However, I noticed that GitHub now marks your commit as unverified since it didn’t come from your GPG key, and I want to respect your authorship standards.

If you would like to force push a signed commit and tag me I'll make sure this gets reviewed. Sorry for the trouble but looking forward to getting these migration pulls and issues closed out.

[willnode]

You can force push again to the original commit 25697bc which should restore this PR

[cstockton]

@willnode Since you are okay with losing authorship I've restored the prior commit. Thank you!

[cstockton]

👍

[siennathesane]

@willnode when I wrote this, I had included your fixes plus my own. Didn't mean to erase your contribution at all! 🫶

[willnode]

LGTM

[coveralls]

Pull Request Test Coverage Report for Build 20113075029

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 68.527%

---

Totals
Change from base Build 20080137533:	0.0%
Covered Lines:	14682
Relevant Lines:	21425

---

💛 - Coveralls

[bartcode]

Could this be merged still, @willnode ? There hasn't been an update in two months even though everything is good to go. A lot of people must be waiting for this issue to be fixed.

@siennathesane , thank you for this fix! I ran into this exact same issue and luckily found your open PR.

[cstockton]

Sorry for the delay here, I'll merge this after tests run.

[siennathesane]

What kind of change does this PR introduce?

Big fix for #1729, #1848, #1983, and #2040 with an additional type fix.

What is the current behavior?

The auth service cannot be deployed in a net new environment on PostgreSQL 17.

What is the new behavior?

The service is running properly with PostgreSQL 17 in a cleanroom environment.

Additional context

Here is a redacted version of the terraform I used to deploy it with. I used my own container build with these fixes, ghcr.io/siennathesane/auth:v2.175.0, that you can use to verify the fix is valid, if you want.

locals {
f2-auth-db-namespace="auth"
}
resource"kubernetes_service_account""f2-auth" {
metadata {
name="f2-auth"namespace=var.namespace
}
}
resource"kubernetes_manifest""f2-auth-db" {
manifest={
"apiVersion"="postgresql.cnpg.io/v1""kind"="Database""metadata"= {
"name"="f2-auth-db""namespace"= var.namespace
}
"spec"= {
"cluster"= {
"name"= kubernetes_manifest.f2-cluster.object.metadata.name
}
"allowConnections"=true"name"= local.f2-auth-db-namespace
"owner"= kubernetes_secret_v1.f2-auth-db.data.username
"schemas"= [{
"name"= local.f2-auth-db-namespace
"owner"= kubernetes_secret_v1.f2-auth-db.data.username
}]
}
}
}
resource"kubernetes_config_map_v1""f2-auth-initdb" {
metadata {
name="sql-commands"namespace=var.namespace
}
data={
"script.sql"=<<-EOT ALTER USER ${kubernetes_secret_v1.f2-auth-db.data.username} WITH LOGIN CREATEROLE CREATEDB REPLICATION BYPASSRLS; GRANT ${kubernetes_secret_v1.f2-auth-db.data.username} TO postgres; CREATE SCHEMA IF NOT EXISTS ${local.f2-auth-db-namespace} AUTHORIZATION ${kubernetes_secret_v1.f2-auth-db.data.username}; GRANT CREATE ON DATABASE postgres TO ${kubernetes_secret_v1.f2-auth-db.data.username}; ALTER USER ${kubernetes_secret_v1.f2-auth-db.data.username} SET search_path = '${local.f2-auth-db-namespace}'; EOT
}
}
resource"kubernetes_secret_v1""f2-auth-db" {
metadata {
name="auth-db"namespace=var.namespacelabels={
"cnpg.io/reload"="true"
}
}
data={
username ="[REDACTED]"
password = random_password.f2-auth-db-password.result
database ="auth"
}
type="kubernetes.io/basic-auth"
}
resource"kubernetes_secret_v1""f2-auth-jwt" {
metadata {
name="auth-jwt"namespace=var.namespace
}
data={
anonKey ="[REDACTED]"
secret ="[REDACTED]"
serviceKey ="[REDACTED]"
}
type="Opaque"
}
resource"random_password""f2-auth-db-password" {
length=16special=false
}
resource"kubernetes_deployment_v1""f2-auth" {
depends_on=[kubernetes_manifest.f2-auth-db]
timeouts {
create="2m"
}
metadata {
name="f2auth"labels={
"f2.pub/app"="auth-${var.environment}"
}
namespace=var.namespace
}
spec {
replicas=1selector {
match_labels={
"f2.pub/app"="auth-${var.environment}"
}
}
template {
metadata {
labels={
"f2.pub/app"="auth-${var.environment}"
}
}
spec {
image_pull_secrets { name=var.ghcr-pull-secret-name }
init_container {
name="init-db"image="postgres:17-alpine"command=["psql", "-f", "/sql/script.sql"]
env {
name="PGHOST"value="${kubernetes_manifest.f2-cluster.object.metadata.name}-rw"
}
env {
name="PGPORT"value="5432"
}
env {
name="PGDATABASE"value=kubernetes_secret_v1.f2-auth-db.data.database
}
env {
name="PGUSER"value=kubernetes_secret_v1.f2-auth-db.data.username
}
env {
name="PGPASSWORD"value=kubernetes_secret_v1.f2-auth-db.data.password
}
volume_mount {
name="sql-volume"mount_path="/sql"
}
}
volume {
name="sql-volume"config_map {
name=kubernetes_config_map_v1.f2-auth-initdb.metadata[0].name
}
}
container {
image="ghcr.io/siennathesane/auth:${var.goauth-version}"image_pull_policy="Always"name="auth"resources {
limits={
cpu ="0.5"
memory ="512Mi"
}
requests={
cpu ="250m"
memory ="50Mi"
}
}
port {
name="http"container_port=9999protocol="TCP"
}
env {
name="GOTRUE_DB_DRIVER"value="postgres"
}
env {
name="DB_NAMESPACE"value="auth"
}
env {
name="DATABASE_URL"value="postgres://${kubernetes_secret_v1.f2-auth-db.data.username}:[REDACTED]@${kubernetes_manifest.f2-cluster.object.metadata.name}-rw:5432/${kubernetes_secret_v1.f2-auth-db.data.database}"
}
env {
name="GOTRUE_JWT_SECRET"value_from {
secret_key_ref {
name="auth-jwt"key="secret"
}
}
}
env {
name="API_EXTERNAL_URL"value="http://[REDACTED]"
}
env {
name="GOTRUE_SITE_URL"value="http://[REDACTED]"
}
env {
name="GOTRUE_API_HOST"value="0.0.0.0"
}
env {
name="PORT"value="9999"
}
}
}
}
}
}

Closes#1729
Closes#1848
Closes#1983
Closes#2040

[siennathesane]

@kangmingtay can you please review this so it can get merged? It's an ongoing issue for a lot for people.

[willnode]

+1

[siennathesane]

I guess supabase really doesn't care about OSS contributions

[cstockton]

Hi @siennathesane@willnode — First I wanted to say we do care and appreciate both your contributions very much. Sorry for the delay on these reviews, I'll bring this up with the team to brainstorm how to improve.

I reviewed all the migration related PRs/issues and wanted to ensure the original contributions from @willnode (#1983, #2040) and the (id::text = user_id::text fix) in #2047 were preserved correctly so I was going to create a new PR with everything cherry picked.

I mistakingly force pushed to the wrong upstream after cherry picking 1983 & 2040, which lost the ID change. To try to fix this I reintroduced your id migration fix as a separate commit using your previous git log message and commit. However, I noticed that GitHub now marks your commit as unverified since it didn’t come from your GPG key, and I want to respect your authorship standards.

If you would like to force push a signed commit and tag me I'll make sure this gets reviewed. Sorry for the trouble but looking forward to getting these migration pulls and issues closed out.

[willnode]

You can force push again to the original commit 25697bc which should restore this PR

[cstockton]

@willnode Since you are okay with losing authorship I've restored the prior commit. Thank you!

[cstockton]

👍

[siennathesane]

@willnode when I wrote this, I had included your fixes plus my own. Didn't mean to erase your contribution at all! 🫶

[willnode]

LGTM

[coveralls]

Pull Request Test Coverage Report for Build 20113075029

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 68.527%

---

Totals
Change from base Build 20080137533:	0.0%
Covered Lines:	14682
Relevant Lines:	21425

---

💛 - Coveralls

[bartcode]

Could this be merged still, @willnode ? There hasn't been an update in two months even though everything is good to go. A lot of people must be waiting for this issue to be fixed.

@siennathesane , thank you for this fix! I ran into this exact same issue and luckily found your open PR.

[cstockton]

Sorry for the delay here, I'll merge this after tests run.

[siennathesane]

What kind of change does this PR introduce?

Big fix for #1729, #1848, #1983, and #2040 with an additional type fix.

What is the current behavior?

The auth service cannot be deployed in a net new environment on PostgreSQL 17.

What is the new behavior?

The service is running properly with PostgreSQL 17 in a cleanroom environment.

Additional context

Here is a redacted version of the terraform I used to deploy it with. I used my own container build with these fixes, ghcr.io/siennathesane/auth:v2.175.0, that you can use to verify the fix is valid, if you want.

locals {
f2-auth-db-namespace="auth"
}
resource"kubernetes_service_account""f2-auth" {
metadata {
name="f2-auth"namespace=var.namespace
}
}
resource"kubernetes_manifest""f2-auth-db" {
manifest={
"apiVersion"="postgresql.cnpg.io/v1""kind"="Database""metadata"= {
"name"="f2-auth-db""namespace"= var.namespace
}
"spec"= {
"cluster"= {
"name"= kubernetes_manifest.f2-cluster.object.metadata.name
}
"allowConnections"=true"name"= local.f2-auth-db-namespace
"owner"= kubernetes_secret_v1.f2-auth-db.data.username
"schemas"= [{
"name"= local.f2-auth-db-namespace
"owner"= kubernetes_secret_v1.f2-auth-db.data.username
}]
}
}
}
resource"kubernetes_config_map_v1""f2-auth-initdb" {
metadata {
name="sql-commands"namespace=var.namespace
}
data={
"script.sql"=<<-EOT ALTER USER ${kubernetes_secret_v1.f2-auth-db.data.username} WITH LOGIN CREATEROLE CREATEDB REPLICATION BYPASSRLS; GRANT ${kubernetes_secret_v1.f2-auth-db.data.username} TO postgres; CREATE SCHEMA IF NOT EXISTS ${local.f2-auth-db-namespace} AUTHORIZATION ${kubernetes_secret_v1.f2-auth-db.data.username}; GRANT CREATE ON DATABASE postgres TO ${kubernetes_secret_v1.f2-auth-db.data.username}; ALTER USER ${kubernetes_secret_v1.f2-auth-db.data.username} SET search_path = '${local.f2-auth-db-namespace}'; EOT
}
}
resource"kubernetes_secret_v1""f2-auth-db" {
metadata {
name="auth-db"namespace=var.namespacelabels={
"cnpg.io/reload"="true"
}
}
data={
username ="[REDACTED]"
password = random_password.f2-auth-db-password.result
database ="auth"
}
type="kubernetes.io/basic-auth"
}
resource"kubernetes_secret_v1""f2-auth-jwt" {
metadata {
name="auth-jwt"namespace=var.namespace
}
data={
anonKey ="[REDACTED]"
secret ="[REDACTED]"
serviceKey ="[REDACTED]"
}
type="Opaque"
}
resource"random_password""f2-auth-db-password" {
length=16special=false
}
resource"kubernetes_deployment_v1""f2-auth" {
depends_on=[kubernetes_manifest.f2-auth-db]
timeouts {
create="2m"
}
metadata {
name="f2auth"labels={
"f2.pub/app"="auth-${var.environment}"
}
namespace=var.namespace
}
spec {
replicas=1selector {
match_labels={
"f2.pub/app"="auth-${var.environment}"
}
}
template {
metadata {
labels={
"f2.pub/app"="auth-${var.environment}"
}
}
spec {
image_pull_secrets { name=var.ghcr-pull-secret-name }
init_container {
name="init-db"image="postgres:17-alpine"command=["psql", "-f", "/sql/script.sql"]
env {
name="PGHOST"value="${kubernetes_manifest.f2-cluster.object.metadata.name}-rw"
}
env {
name="PGPORT"value="5432"
}
env {
name="PGDATABASE"value=kubernetes_secret_v1.f2-auth-db.data.database
}
env {
name="PGUSER"value=kubernetes_secret_v1.f2-auth-db.data.username
}
env {
name="PGPASSWORD"value=kubernetes_secret_v1.f2-auth-db.data.password
}
volume_mount {
name="sql-volume"mount_path="/sql"
}
}
volume {
name="sql-volume"config_map {
name=kubernetes_config_map_v1.f2-auth-initdb.metadata[0].name
}
}
container {
image="ghcr.io/siennathesane/auth:${var.goauth-version}"image_pull_policy="Always"name="auth"resources {
limits={
cpu ="0.5"
memory ="512Mi"
}
requests={
cpu ="250m"
memory ="50Mi"
}
}
port {
name="http"container_port=9999protocol="TCP"
}
env {
name="GOTRUE_DB_DRIVER"value="postgres"
}
env {
name="DB_NAMESPACE"value="auth"
}
env {
name="DATABASE_URL"value="postgres://${kubernetes_secret_v1.f2-auth-db.data.username}:[REDACTED]@${kubernetes_manifest.f2-cluster.object.metadata.name}-rw:5432/${kubernetes_secret_v1.f2-auth-db.data.database}"
}
env {
name="GOTRUE_JWT_SECRET"value_from {
secret_key_ref {
name="auth-jwt"key="secret"
}
}
}
env {
name="API_EXTERNAL_URL"value="http://[REDACTED]"
}
env {
name="GOTRUE_SITE_URL"value="http://[REDACTED]"
}
env {
name="GOTRUE_API_HOST"value="0.0.0.0"
}
env {
name="PORT"value="9999"
}
}
}
}
}
}

Closes#1729
Closes#1848
Closes#1983
Closes#2040

[siennathesane]

@kangmingtay can you please review this so it can get merged? It's an ongoing issue for a lot for people.

[willnode]

+1

[siennathesane]

I guess supabase really doesn't care about OSS contributions

[cstockton]

Hi @siennathesane@willnode — First I wanted to say we do care and appreciate both your contributions very much. Sorry for the delay on these reviews, I'll bring this up with the team to brainstorm how to improve.

I reviewed all the migration related PRs/issues and wanted to ensure the original contributions from @willnode (#1983, #2040) and the (id::text = user_id::text fix) in #2047 were preserved correctly so I was going to create a new PR with everything cherry picked.

I mistakingly force pushed to the wrong upstream after cherry picking 1983 & 2040, which lost the ID change. To try to fix this I reintroduced your id migration fix as a separate commit using your previous git log message and commit. However, I noticed that GitHub now marks your commit as unverified since it didn’t come from your GPG key, and I want to respect your authorship standards.

If you would like to force push a signed commit and tag me I'll make sure this gets reviewed. Sorry for the trouble but looking forward to getting these migration pulls and issues closed out.

[willnode]

You can force push again to the original commit 25697bc which should restore this PR

[cstockton]

@willnode Since you are okay with losing authorship I've restored the prior commit. Thank you!

[cstockton]

👍

[siennathesane]

@willnode when I wrote this, I had included your fixes plus my own. Didn't mean to erase your contribution at all! 🫶

[willnode]

LGTM

[coveralls]

Pull Request Test Coverage Report for Build 20113075029

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 68.527%

---

Totals
Change from base Build 20080137533:	0.0%
Covered Lines:	14682
Relevant Lines:	21425

---

💛 - Coveralls

[bartcode]

Could this be merged still, @willnode ? There hasn't been an update in two months even though everything is good to go. A lot of people must be waiting for this issue to be fixed.

@siennathesane , thank you for this fix! I ran into this exact same issue and luckily found your open PR.

[cstockton]

Sorry for the delay here, I'll merge this after tests run.

[siennathesane]

What kind of change does this PR introduce?

Big fix for #1729, #1848, #1983, and #2040 with an additional type fix.

What is the current behavior?

The auth service cannot be deployed in a net new environment on PostgreSQL 17.

What is the new behavior?

The service is running properly with PostgreSQL 17 in a cleanroom environment.

Additional context

Here is a redacted version of the terraform I used to deploy it with. I used my own container build with these fixes, ghcr.io/siennathesane/auth:v2.175.0, that you can use to verify the fix is valid, if you want.

locals {
f2-auth-db-namespace="auth"
}
resource"kubernetes_service_account""f2-auth" {
metadata {
name="f2-auth"namespace=var.namespace
}
}
resource"kubernetes_manifest""f2-auth-db" {
manifest={
"apiVersion"="postgresql.cnpg.io/v1""kind"="Database""metadata"= {
"name"="f2-auth-db""namespace"= var.namespace
}
"spec"= {
"cluster"= {
"name"= kubernetes_manifest.f2-cluster.object.metadata.name
}
"allowConnections"=true"name"= local.f2-auth-db-namespace
"owner"= kubernetes_secret_v1.f2-auth-db.data.username
"schemas"= [{
"name"= local.f2-auth-db-namespace
"owner"= kubernetes_secret_v1.f2-auth-db.data.username
}]
}
}
}
resource"kubernetes_config_map_v1""f2-auth-initdb" {
metadata {
name="sql-commands"namespace=var.namespace
}
data={
"script.sql"=<<-EOT ALTER USER ${kubernetes_secret_v1.f2-auth-db.data.username} WITH LOGIN CREATEROLE CREATEDB REPLICATION BYPASSRLS; GRANT ${kubernetes_secret_v1.f2-auth-db.data.username} TO postgres; CREATE SCHEMA IF NOT EXISTS ${local.f2-auth-db-namespace} AUTHORIZATION ${kubernetes_secret_v1.f2-auth-db.data.username}; GRANT CREATE ON DATABASE postgres TO ${kubernetes_secret_v1.f2-auth-db.data.username}; ALTER USER ${kubernetes_secret_v1.f2-auth-db.data.username} SET search_path = '${local.f2-auth-db-namespace}'; EOT
}
}
resource"kubernetes_secret_v1""f2-auth-db" {
metadata {
name="auth-db"namespace=var.namespacelabels={
"cnpg.io/reload"="true"
}
}
data={
username ="[REDACTED]"
password = random_password.f2-auth-db-password.result
database ="auth"
}
type="kubernetes.io/basic-auth"
}
resource"kubernetes_secret_v1""f2-auth-jwt" {
metadata {
name="auth-jwt"namespace=var.namespace
}
data={
anonKey ="[REDACTED]"
secret ="[REDACTED]"
serviceKey ="[REDACTED]"
}
type="Opaque"
}
resource"random_password""f2-auth-db-password" {
length=16special=false
}
resource"kubernetes_deployment_v1""f2-auth" {
depends_on=[kubernetes_manifest.f2-auth-db]
timeouts {
create="2m"
}
metadata {
name="f2auth"labels={
"f2.pub/app"="auth-${var.environment}"
}
namespace=var.namespace
}
spec {
replicas=1selector {
match_labels={
"f2.pub/app"="auth-${var.environment}"
}
}
template {
metadata {
labels={
"f2.pub/app"="auth-${var.environment}"
}
}
spec {
image_pull_secrets { name=var.ghcr-pull-secret-name }
init_container {
name="init-db"image="postgres:17-alpine"command=["psql", "-f", "/sql/script.sql"]
env {
name="PGHOST"value="${kubernetes_manifest.f2-cluster.object.metadata.name}-rw"
}
env {
name="PGPORT"value="5432"
}
env {
name="PGDATABASE"value=kubernetes_secret_v1.f2-auth-db.data.database
}
env {
name="PGUSER"value=kubernetes_secret_v1.f2-auth-db.data.username
}
env {
name="PGPASSWORD"value=kubernetes_secret_v1.f2-auth-db.data.password
}
volume_mount {
name="sql-volume"mount_path="/sql"
}
}
volume {
name="sql-volume"config_map {
name=kubernetes_config_map_v1.f2-auth-initdb.metadata[0].name
}
}
container {
image="ghcr.io/siennathesane/auth:${var.goauth-version}"image_pull_policy="Always"name="auth"resources {
limits={
cpu ="0.5"
memory ="512Mi"
}
requests={
cpu ="250m"
memory ="50Mi"
}
}
port {
name="http"container_port=9999protocol="TCP"
}
env {
name="GOTRUE_DB_DRIVER"value="postgres"
}
env {
name="DB_NAMESPACE"value="auth"
}
env {
name="DATABASE_URL"value="postgres://${kubernetes_secret_v1.f2-auth-db.data.username}:[REDACTED]@${kubernetes_manifest.f2-cluster.object.metadata.name}-rw:5432/${kubernetes_secret_v1.f2-auth-db.data.database}"
}
env {
name="GOTRUE_JWT_SECRET"value_from {
secret_key_ref {
name="auth-jwt"key="secret"
}
}
}
env {
name="API_EXTERNAL_URL"value="http://[REDACTED]"
}
env {
name="GOTRUE_SITE_URL"value="http://[REDACTED]"
}
env {
name="GOTRUE_API_HOST"value="0.0.0.0"
}
env {
name="PORT"value="9999"
}
}
}
}
}
}

Closes#1729
Closes#1848
Closes#1983
Closes#2040

[siennathesane]

@kangmingtay can you please review this so it can get merged? It's an ongoing issue for a lot for people.

[willnode]

+1

[siennathesane]

I guess supabase really doesn't care about OSS contributions

[cstockton]

Hi @siennathesane@willnode — First I wanted to say we do care and appreciate both your contributions very much. Sorry for the delay on these reviews, I'll bring this up with the team to brainstorm how to improve.

I reviewed all the migration related PRs/issues and wanted to ensure the original contributions from @willnode (#1983, #2040) and the (id::text = user_id::text fix) in #2047 were preserved correctly so I was going to create a new PR with everything cherry picked.

I mistakingly force pushed to the wrong upstream after cherry picking 1983 & 2040, which lost the ID change. To try to fix this I reintroduced your id migration fix as a separate commit using your previous git log message and commit. However, I noticed that GitHub now marks your commit as unverified since it didn’t come from your GPG key, and I want to respect your authorship standards.

If you would like to force push a signed commit and tag me I'll make sure this gets reviewed. Sorry for the trouble but looking forward to getting these migration pulls and issues closed out.

[willnode]

You can force push again to the original commit 25697bc which should restore this PR

[cstockton]

@willnode Since you are okay with losing authorship I've restored the prior commit. Thank you!

[cstockton]

👍

[siennathesane]

@willnode when I wrote this, I had included your fixes plus my own. Didn't mean to erase your contribution at all! 🫶

[willnode]

LGTM

[coveralls]

Pull Request Test Coverage Report for Build 20113075029

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 68.527%

---

Totals
Change from base Build 20080137533:	0.0%
Covered Lines:	14682
Relevant Lines:	21425

---

💛 - Coveralls

[bartcode]

Could this be merged still, @willnode ? There hasn't been an update in two months even though everything is good to go. A lot of people must be waiting for this issue to be fixed.

@siennathesane , thank you for this fix! I ran into this exact same issue and luckily found your open PR.

[cstockton]

Sorry for the delay here, I'll merge this after tests run.

[siennathesane]

What kind of change does this PR introduce?

Big fix for #1729, #1848, #1983, and #2040 with an additional type fix.

What is the current behavior?

The auth service cannot be deployed in a net new environment on PostgreSQL 17.

What is the new behavior?

The service is running properly with PostgreSQL 17 in a cleanroom environment.

Additional context

Here is a redacted version of the terraform I used to deploy it with. I used my own container build with these fixes, ghcr.io/siennathesane/auth:v2.175.0, that you can use to verify the fix is valid, if you want.

locals {
f2-auth-db-namespace="auth"
}
resource"kubernetes_service_account""f2-auth" {
metadata {
name="f2-auth"namespace=var.namespace
}
}
resource"kubernetes_manifest""f2-auth-db" {
manifest={
"apiVersion"="postgresql.cnpg.io/v1""kind"="Database""metadata"= {
"name"="f2-auth-db""namespace"= var.namespace
}
"spec"= {
"cluster"= {
"name"= kubernetes_manifest.f2-cluster.object.metadata.name
}
"allowConnections"=true"name"= local.f2-auth-db-namespace
"owner"= kubernetes_secret_v1.f2-auth-db.data.username
"schemas"= [{
"name"= local.f2-auth-db-namespace
"owner"= kubernetes_secret_v1.f2-auth-db.data.username
}]
}
}
}
resource"kubernetes_config_map_v1""f2-auth-initdb" {
metadata {
name="sql-commands"namespace=var.namespace
}
data={
"script.sql"=<<-EOT ALTER USER ${kubernetes_secret_v1.f2-auth-db.data.username} WITH LOGIN CREATEROLE CREATEDB REPLICATION BYPASSRLS; GRANT ${kubernetes_secret_v1.f2-auth-db.data.username} TO postgres; CREATE SCHEMA IF NOT EXISTS ${local.f2-auth-db-namespace} AUTHORIZATION ${kubernetes_secret_v1.f2-auth-db.data.username}; GRANT CREATE ON DATABASE postgres TO ${kubernetes_secret_v1.f2-auth-db.data.username}; ALTER USER ${kubernetes_secret_v1.f2-auth-db.data.username} SET search_path = '${local.f2-auth-db-namespace}'; EOT
}
}
resource"kubernetes_secret_v1""f2-auth-db" {
metadata {
name="auth-db"namespace=var.namespacelabels={
"cnpg.io/reload"="true"
}
}
data={
username ="[REDACTED]"
password = random_password.f2-auth-db-password.result
database ="auth"
}
type="kubernetes.io/basic-auth"
}
resource"kubernetes_secret_v1""f2-auth-jwt" {
metadata {
name="auth-jwt"namespace=var.namespace
}
data={
anonKey ="[REDACTED]"
secret ="[REDACTED]"
serviceKey ="[REDACTED]"
}
type="Opaque"
}
resource"random_password""f2-auth-db-password" {
length=16special=false
}
resource"kubernetes_deployment_v1""f2-auth" {
depends_on=[kubernetes_manifest.f2-auth-db]
timeouts {
create="2m"
}
metadata {
name="f2auth"labels={
"f2.pub/app"="auth-${var.environment}"
}
namespace=var.namespace
}
spec {
replicas=1selector {
match_labels={
"f2.pub/app"="auth-${var.environment}"
}
}
template {
metadata {
labels={
"f2.pub/app"="auth-${var.environment}"
}
}
spec {
image_pull_secrets { name=var.ghcr-pull-secret-name }
init_container {
name="init-db"image="postgres:17-alpine"command=["psql", "-f", "/sql/script.sql"]
env {
name="PGHOST"value="${kubernetes_manifest.f2-cluster.object.metadata.name}-rw"
}
env {
name="PGPORT"value="5432"
}
env {
name="PGDATABASE"value=kubernetes_secret_v1.f2-auth-db.data.database
}
env {
name="PGUSER"value=kubernetes_secret_v1.f2-auth-db.data.username
}
env {
name="PGPASSWORD"value=kubernetes_secret_v1.f2-auth-db.data.password
}
volume_mount {
name="sql-volume"mount_path="/sql"
}
}
volume {
name="sql-volume"config_map {
name=kubernetes_config_map_v1.f2-auth-initdb.metadata[0].name
}
}
container {
image="ghcr.io/siennathesane/auth:${var.goauth-version}"image_pull_policy="Always"name="auth"resources {
limits={
cpu ="0.5"
memory ="512Mi"
}
requests={
cpu ="250m"
memory ="50Mi"
}
}
port {
name="http"container_port=9999protocol="TCP"
}
env {
name="GOTRUE_DB_DRIVER"value="postgres"
}
env {
name="DB_NAMESPACE"value="auth"
}
env {
name="DATABASE_URL"value="postgres://${kubernetes_secret_v1.f2-auth-db.data.username}:[REDACTED]@${kubernetes_manifest.f2-cluster.object.metadata.name}-rw:5432/${kubernetes_secret_v1.f2-auth-db.data.database}"
}
env {
name="GOTRUE_JWT_SECRET"value_from {
secret_key_ref {
name="auth-jwt"key="secret"
}
}
}
env {
name="API_EXTERNAL_URL"value="http://[REDACTED]"
}
env {
name="GOTRUE_SITE_URL"value="http://[REDACTED]"
}
env {
name="GOTRUE_API_HOST"value="0.0.0.0"
}
env {
name="PORT"value="9999"
}
}
}
}
}
}

Closes#1729
Closes#1848
Closes#1983
Closes#2040

[siennathesane]

@kangmingtay can you please review this so it can get merged? It's an ongoing issue for a lot for people.

[willnode]

+1

[siennathesane]

I guess supabase really doesn't care about OSS contributions

[cstockton]

Hi @siennathesane@willnode — First I wanted to say we do care and appreciate both your contributions very much. Sorry for the delay on these reviews, I'll bring this up with the team to brainstorm how to improve.

I reviewed all the migration related PRs/issues and wanted to ensure the original contributions from @willnode (#1983, #2040) and the (id::text = user_id::text fix) in #2047 were preserved correctly so I was going to create a new PR with everything cherry picked.

I mistakingly force pushed to the wrong upstream after cherry picking 1983 & 2040, which lost the ID change. To try to fix this I reintroduced your id migration fix as a separate commit using your previous git log message and commit. However, I noticed that GitHub now marks your commit as unverified since it didn’t come from your GPG key, and I want to respect your authorship standards.

If you would like to force push a signed commit and tag me I'll make sure this gets reviewed. Sorry for the trouble but looking forward to getting these migration pulls and issues closed out.

[willnode]

You can force push again to the original commit 25697bc which should restore this PR

[cstockton]

@willnode Since you are okay with losing authorship I've restored the prior commit. Thank you!

[cstockton]

👍

[siennathesane]

@willnode when I wrote this, I had included your fixes plus my own. Didn't mean to erase your contribution at all! 🫶

[willnode]

LGTM

[coveralls]

Pull Request Test Coverage Report for Build 20113075029

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 68.527%

---

Totals
Change from base Build 20080137533:	0.0%
Covered Lines:	14682
Relevant Lines:	21425

---

💛 - Coveralls

[bartcode]

Could this be merged still, @willnode ? There hasn't been an update in two months even though everything is good to go. A lot of people must be waiting for this issue to be fixed.

@siennathesane , thank you for this fix! I ran into this exact same issue and luckily found your open PR.

[cstockton]

Sorry for the delay here, I'll merge this after tests run.

[siennathesane]

What kind of change does this PR introduce?

Big fix for #1729, #1848, #1983, and #2040 with an additional type fix.

What is the current behavior?

The auth service cannot be deployed in a net new environment on PostgreSQL 17.

What is the new behavior?

The service is running properly with PostgreSQL 17 in a cleanroom environment.

Additional context

Here is a redacted version of the terraform I used to deploy it with. I used my own container build with these fixes, ghcr.io/siennathesane/auth:v2.175.0, that you can use to verify the fix is valid, if you want.

locals {
f2-auth-db-namespace="auth"
}
resource"kubernetes_service_account""f2-auth" {
metadata {
name="f2-auth"namespace=var.namespace
}
}
resource"kubernetes_manifest""f2-auth-db" {
manifest={
"apiVersion"="postgresql.cnpg.io/v1""kind"="Database""metadata"= {
"name"="f2-auth-db""namespace"= var.namespace
}
"spec"= {
"cluster"= {
"name"= kubernetes_manifest.f2-cluster.object.metadata.name
}
"allowConnections"=true"name"= local.f2-auth-db-namespace
"owner"= kubernetes_secret_v1.f2-auth-db.data.username
"schemas"= [{
"name"= local.f2-auth-db-namespace
"owner"= kubernetes_secret_v1.f2-auth-db.data.username
}]
}
}
}
resource"kubernetes_config_map_v1""f2-auth-initdb" {
metadata {
name="sql-commands"namespace=var.namespace
}
data={
"script.sql"=<<-EOT ALTER USER ${kubernetes_secret_v1.f2-auth-db.data.username} WITH LOGIN CREATEROLE CREATEDB REPLICATION BYPASSRLS; GRANT ${kubernetes_secret_v1.f2-auth-db.data.username} TO postgres; CREATE SCHEMA IF NOT EXISTS ${local.f2-auth-db-namespace} AUTHORIZATION ${kubernetes_secret_v1.f2-auth-db.data.username}; GRANT CREATE ON DATABASE postgres TO ${kubernetes_secret_v1.f2-auth-db.data.username}; ALTER USER ${kubernetes_secret_v1.f2-auth-db.data.username} SET search_path = '${local.f2-auth-db-namespace}'; EOT
}
}
resource"kubernetes_secret_v1""f2-auth-db" {
metadata {
name="auth-db"namespace=var.namespacelabels={
"cnpg.io/reload"="true"
}
}
data={
username ="[REDACTED]"
password = random_password.f2-auth-db-password.result
database ="auth"
}
type="kubernetes.io/basic-auth"
}
resource"kubernetes_secret_v1""f2-auth-jwt" {
metadata {
name="auth-jwt"namespace=var.namespace
}
data={
anonKey ="[REDACTED]"
secret ="[REDACTED]"
serviceKey ="[REDACTED]"
}
type="Opaque"
}
resource"random_password""f2-auth-db-password" {
length=16special=false
}
resource"kubernetes_deployment_v1""f2-auth" {
depends_on=[kubernetes_manifest.f2-auth-db]
timeouts {
create="2m"
}
metadata {
name="f2auth"labels={
"f2.pub/app"="auth-${var.environment}"
}
namespace=var.namespace
}
spec {
replicas=1selector {
match_labels={
"f2.pub/app"="auth-${var.environment}"
}
}
template {
metadata {
labels={
"f2.pub/app"="auth-${var.environment}"
}
}
spec {
image_pull_secrets { name=var.ghcr-pull-secret-name }
init_container {
name="init-db"image="postgres:17-alpine"command=["psql", "-f", "/sql/script.sql"]
env {
name="PGHOST"value="${kubernetes_manifest.f2-cluster.object.metadata.name}-rw"
}
env {
name="PGPORT"value="5432"
}
env {
name="PGDATABASE"value=kubernetes_secret_v1.f2-auth-db.data.database
}
env {
name="PGUSER"value=kubernetes_secret_v1.f2-auth-db.data.username
}
env {
name="PGPASSWORD"value=kubernetes_secret_v1.f2-auth-db.data.password
}
volume_mount {
name="sql-volume"mount_path="/sql"
}
}
volume {
name="sql-volume"config_map {
name=kubernetes_config_map_v1.f2-auth-initdb.metadata[0].name
}
}
container {
image="ghcr.io/siennathesane/auth:${var.goauth-version}"image_pull_policy="Always"name="auth"resources {
limits={
cpu ="0.5"
memory ="512Mi"
}
requests={
cpu ="250m"
memory ="50Mi"
}
}
port {
name="http"container_port=9999protocol="TCP"
}
env {
name="GOTRUE_DB_DRIVER"value="postgres"
}
env {
name="DB_NAMESPACE"value="auth"
}
env {
name="DATABASE_URL"value="postgres://${kubernetes_secret_v1.f2-auth-db.data.username}:[REDACTED]@${kubernetes_manifest.f2-cluster.object.metadata.name}-rw:5432/${kubernetes_secret_v1.f2-auth-db.data.database}"
}
env {
name="GOTRUE_JWT_SECRET"value_from {
secret_key_ref {
name="auth-jwt"key="secret"
}
}
}
env {
name="API_EXTERNAL_URL"value="http://[REDACTED]"
}
env {
name="GOTRUE_SITE_URL"value="http://[REDACTED]"
}
env {
name="GOTRUE_API_HOST"value="0.0.0.0"
}
env {
name="PORT"value="9999"
}
}
}
}
}
}

Closes#1729
Closes#1848
Closes#1983
Closes#2040

[siennathesane]

@kangmingtay can you please review this so it can get merged? It's an ongoing issue for a lot for people.

[willnode]

+1

[siennathesane]

I guess supabase really doesn't care about OSS contributions

[cstockton]

Hi @siennathesane@willnode — First I wanted to say we do care and appreciate both your contributions very much. Sorry for the delay on these reviews, I'll bring this up with the team to brainstorm how to improve.

I reviewed all the migration related PRs/issues and wanted to ensure the original contributions from @willnode (#1983, #2040) and the (id::text = user_id::text fix) in #2047 were preserved correctly so I was going to create a new PR with everything cherry picked.

I mistakingly force pushed to the wrong upstream after cherry picking 1983 & 2040, which lost the ID change. To try to fix this I reintroduced your id migration fix as a separate commit using your previous git log message and commit. However, I noticed that GitHub now marks your commit as unverified since it didn’t come from your GPG key, and I want to respect your authorship standards.

If you would like to force push a signed commit and tag me I'll make sure this gets reviewed. Sorry for the trouble but looking forward to getting these migration pulls and issues closed out.

[willnode]

You can force push again to the original commit 25697bc which should restore this PR

[cstockton]

@willnode Since you are okay with losing authorship I've restored the prior commit. Thank you!

[cstockton]

👍

[siennathesane]

@willnode when I wrote this, I had included your fixes plus my own. Didn't mean to erase your contribution at all! 🫶

[willnode]

LGTM

[coveralls]

Pull Request Test Coverage Report for Build 20113075029

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 68.527%

---

Totals
Change from base Build 20080137533:	0.0%
Covered Lines:	14682
Relevant Lines:	21425

---

💛 - Coveralls

[bartcode]

Could this be merged still, @willnode ? There hasn't been an update in two months even though everything is good to go. A lot of people must be waiting for this issue to be fixed.

@siennathesane , thank you for this fix! I ran into this exact same issue and luckily found your open PR.

[cstockton]

Sorry for the delay here, I'll merge this after tests run.