Skip to content

Supabase bootstrapping #157

@prskr

Description

@prskr

Hi,

first of all I'd like to thank you for this great project!

I'm currently looking into using operator to automate on-premises Supabase database bootstrapping and unfortunately there are some limitations:

  • Supabase creates extensions WITH SCHEMA which isn't supported right now
  • Supabase creates schemas WITH AUTHORIZATION which isn't supported right now as well
  • it's not possible to customize the 'managed' DB after creation apart from schemas and extensions e.g. by running some initial migrations

Of course these limitations are not solely related to Supabase but I couldn't come up with a better title 😅

I could completely understand if you don't want to change semantics or if you would argue that DB initialisation is up to the app user, I just figured I'd ask whether you'd be open to some PRs.

I'm afraid the first two points would require a v1alpha2 schema upgrade but that could be automated for existing users so they wouldn't experience any issues?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions