Skip to content

Conversation

sdedovic
Copy link

@sdedovic sdedovic commented Apr 10, 2025

What kind of change does this PR introduce?

Doc Update

What is the current behavior?

This works for me with the following (abridged) terraform configuration:

terraform {
  required_providers {
    supabase = {
      source  = "supabase/supabase"
      version = "~> 1.0"
    }
  }
}

Not sure why this behavior isn't documented by y'all, makes using the provider in automated places much easier.

@sdedovic
Copy link
Author

No idea why the PR checks are failing this is simply a documentation update

@sdedovic
Copy link
Author

Also maybe consider adding it to your README and the docs here too?

@shellscape
Copy link

you might want to check out https://github.com/shellscape/terraform-provider-supabase. covers a lot of the shortfalls of the official provider.

@sdedovic
Copy link
Author

you might want to check out https://github.com/shellscape/terraform-provider-supabase. covers a lot of the shortfalls of the official provider.

thanks! I didn't know this existed. I actually switched to RDS instead, and this official provider + completely lacking documentation was the main reason why.

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

Successfully merging this pull request may close these issues.

2 participants