feat: support create/delete project

[S96EA]

What kind of change does this PR introduce?

suuport create/delete project

[S96EA]

Added a basic version that works well for creating or deleting projects. Additional tests need to be implemented.

[S96EA]

Added a basic version that works well for creating or deleting projects. Additional tests need to be implemented.

Completed

[sweatybridge]

I made some minor edits based on my local testing. The rest LGTM.

There's still a small issue where remote project states are not synced to local. For eg.

1. Run terraform apply with the following main.tf

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

provider "supabase" {
  access_token = file("${path.module}/access-token")
}

resource "supabase_project" "test" {
  organization_id   = "nknnyrtlhxudbsbuazsu"
  name              = "tf-project"
  database_password = "example-password"
  region            = "ap-southeast-1"
}

2. Delete the generated local state by rm terraform.tfstate. This is equivalent to someone cloning the TF config to start from a fresh state.

3. Run terraform plan and observe that TF wants to create a new test project.

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # supabase_project.staging will be created
  + resource "supabase_project" "staging" {
      + database_password = (sensitive value)
      + id                = (known after apply)
      + name              = "tf-project"
      + organization_id   = "nknnyrtlhxudbsbuazsu"
      + region            = "ap-southeast-1"
    }

I think this happens because we use a generated project ID returned from API. If the local state file doesn't exist, the Id field will default to empty string so it cannot match any of the projects returned from API.

I'm not sure what is the best solution here so any ideas will be appreciated.

[S96EA]

I made some minor edits based on my local testing. The rest LGTM.

There's still a small issue where remote project states are not synced to local. For eg.

1. Run terraform apply with the following main.tf

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

provider "supabase" {
  access_token = file("${path.module}/access-token")
}

resource "supabase_project" "test" {
  organization_id   = "nknnyrtlhxudbsbuazsu"
  name              = "tf-project"
  database_password = "example-password"
  region            = "ap-southeast-1"
}

2. Delete the generated local state by rm terraform.tfstate. This is equivalent to someone cloning the TF config to start from a fresh state.
3. Run terraform plan and observe that TF wants to create a new test project.

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # supabase_project.staging will be created
  + resource "supabase_project" "staging" {
      + database_password = (sensitive value)
      + id                = (known after apply)
      + name              = "tf-project"
      + organization_id   = "nknnyrtlhxudbsbuazsu"
      + region            = "ap-southeast-1"
    }

I think this happens because we use a generated project ID returned from API. If the local state file doesn't exist, the Id field will default to empty string so it cannot match any of the projects returned from API.

I'm not sure what is the best solution here so any ideas will be appreciated.

I attempted to replicate the issue and discovered that Terraform does not invoke the Read method in the absence of a Terraform state file when run terraform plan. Consequently, this prevents the utilization of a fallback approach, such as matching a project using a combination of organization and name when an ID is not available.
However, we can circumvent this limitation by employing the import command to generate a Terraform state file. For instance, you can use terraform import supabase_project.new ztfwpfmyrtiubpbeagvu to accomplish this.

[sweatybridge]

Thanks for suggesting the import command. I ended up adding the import block to main.tf to keep these version controlled. It does require a recent version of terraform but I think it is a good solution.