Skip to content

Conversation

@JEETDESAI25
Copy link

What kind of change does this PR introduce?

Documentation improvement

What is the current behavior?

Closes #218

The organization_id parameter lacks clarity, users don't know it refers to the organization slug found in the dashboard URL. Additionally, import documentation is missing for all resources (project, settings, branch).

What is the new behavior?

  • Updated organization_id schema description to specify it's the organization slug
  • Added custom templates with Import sections for all three resources
  • Added inline comment in README.md example

Additional context

Regenerated docs via go generate ./.... Minor merge conflict possible with PR #255 in project_resource.go (both changes should be kept).

@JEETDESAI25 JEETDESAI25 requested a review from a team as a code owner November 26, 2025 01:35
@JEETDESAI25 JEETDESAI25 force-pushed the fix/issue-218-doc-org-id-import branch from 551e1b7 to 9c162f2 Compare November 26, 2025 01:46
Copy link
Collaborator

@savme savme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for updating the docs, @JEETDESAI25! I think we can use a simpler approach for the import syntax descriptions

}
resource "supabase_project" "production" {
# organization_id is your organization slug (found in dashboard URL)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let’s mark the exact dashboard steps? Should help anyone new find it quickly

Suggested change
# organization_id is your organization slug (found in dashboard URL)
# organization_id is your organization's slug (it can be found in the Supabase Dashboard under Organization Settings > Organization Details > Organization slug)

- `user` (String) User
- `version` (String) Postgres version

## Import
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tfplugindocs supports documenting the import syntax via import.sh files placed in a resource's examples directory. I’d prefer this over modifying the templates, since we don’t really need anything custom there yet.

The usage of import.sh is documented here

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.

Doc - organiaztion_id is for organization slug / missing import

2 participants