Is your feature request related to a problem? Please describe.
Many applications run database migrations on startup or during deployment that execute statements like CREATE TABLE public.projects (...). These migrations expect the database user to be able to create new tables in the target schema, typically public.
Because the operator omits the CREATE grant, the very first migration fails with:
ERROR: permission denied for schema public
Describe the solution you'd like
An optional, declarative way to grant CREATE ON SCHEMA for managed schemas, including public, configurable by role class and/or schema.
Describe alternatives you've considered
Running GRANT CREATE ON SCHEMA public TO role via a Job or manual psql session. This works but undermines the declarative model of the operator.
## Additional context
Not all applications can (easily) be adjusted to not use a default schema of public
Is your feature request related to a problem? Please describe.
Many applications run database migrations on startup or during deployment that execute statements like
CREATE TABLE public.projects (...). These migrations expect the database user to be able to create new tables in the target schema, typicallypublic.Because the operator omits the
CREATEgrant, the very first migration fails with:Describe the solution you'd like
An optional, declarative way to grant
CREATE ON SCHEMAfor managed schemas, includingpublic, configurable by role class and/or schema.Describe alternatives you've considered
Running
GRANT CREATE ON SCHEMA public TO rolevia a Job or manual psql session. This works but undermines the declarative model of the operator.## Additional context
Not all applications can (easily) be adjusted to not use a default schema of
public