Skip to content

added supabase provider - #476

Merged
jeffreyaven merged 2 commits into
devfrom
feature/provider-updates
Oct 12, 2026
Merged

jeffreyaven merged 2 commits into
devfrom
feature/provider-updates

Conversation

@jeffreyaven

Copy link
Copy Markdown
Member

No description provided.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟡 Changes recommended

Several schemas are contradictory, a valid add-on request is rejected, and one path parameter makes the branches specification invalid.

4 open findings
What changed in this PR

Adds a Supabase StackQL provider covering project administration, configuration, observability, and infrastructure APIs.

Changes:

  • Registers bearer authentication and 14 Supabase services.
  • Defines OpenAPI schemas and StackQL SQL verb mappings.
  • Supports project references through SUPABASE_PROJECT_ID.
File Description
provider.yaml Registers Supabase services and authentication.
advisors.yaml Adds performance and security advisors.
analytics.yaml Adds logs, metrics, and usage analytics.
billing.yaml Adds project add-on management.
branches.yaml Adds database branches and action runs.
config.yaml Adds project service configuration APIs.
database.yaml Adds database administration APIs.
domains.yaml Adds custom and vanity domains.
functions.yaml Adds Edge Function management.
network.yaml Adds bans and network restrictions.
organizations.yaml Adds organizations, members, and entitlements.
profile.yaml Adds profile retrieval.
projects.yaml Adds project lifecycle management.
secrets.yaml Adds API key and secret management.
storage.yaml Adds storage bucket listing.

🧠 Review effort: Balanced


💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread providers/src/supabase/v00.00.00000/services/branches.yaml Outdated
type: array
items: {}
error:
type: string
Comment on lines +340 to +358
enum:
- ci_micro
- ci_small
- ci_medium
- ci_large
- ci_xlarge
- ci_2xlarge
- ci_4xlarge
- ci_8xlarge
- ci_12xlarge
- ci_16xlarge
- ci_24xlarge
- ci_24xlarge_optimized_cpu
- ci_24xlarge_optimized_memory
- ci_24xlarge_high_memory
- ci_48xlarge
- ci_48xlarge_optimized_cpu
- ci_48xlarge_optimized_memory
- ci_48xlarge_high_memory
Comment on lines +530 to +541
UpdateCustomHostnameResponseJsonValue:
description: Any JSON-serializable value
anyOf:
- type: string
- type: number
- type: boolean
nullable: true
type: array
items:
$ref: '#/components/schemas/UpdateCustomHostnameResponseJsonValue'
additionalProperties:
$ref: '#/components/schemas/UpdateCustomHostnameResponseJsonValue'
jeffreyaven added a commit to stackql-registry/stackql-provider-supabase that referenced this pull request Oct 12, 2026
An in-path parameter must have a matching {name} placeholder in its
path key. The ref rebase strips ref from the mapped verbs only, so the
skip-coded HEAD action-run count on /actions kept a ref path parameter
the path no longer carries (stackql/stackql-provider-registry#476
review). New rule 8 checks every path-item and operation parameter list
against its path key on all OpenAPI operation verbs and drops orphans -
no names, verbs or paths special-cased. One parameter dropped
(branches.yaml HEAD /actions); idempotent; make test green.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@jeffreyaven
jeffreyaven merged commit 59801e8 into dev Oct 12, 2026
12 checks passed
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