Adding extensions to databases not only to preparedDatabases

[memogarcia]

Please, answer some short questions which should help us to understand your problem / question better?

• Which image of the operator are you using? registry.opensource.zalan.do/acid/spilo-13:2.0-p6
• Where do you run it - cloud or metal? Kubernetes or OpenShift? Bare Metal K8s - Charmed Kubernetes
• Are you running Postgres Operator in production? no
• Type of issue? question

Is it possible to allow the configuration of extensions in databases? At this moment I can only configure extensions on preparedDatabases because preparedDatabases doesn't allow to set users defined in users section to be the owners of that database (or at least the docs doesn't specify how to do this)

What I'm looking to do is one of the following:

  users:
    gitlab:
      - superuser
      - createdb
  databases:
    gitlabhq_production:
      owner: gitlab
      extensions:
        pg_trgm: public
        btree_gist: public

Or

  users:
    gitlab:
      - superuser
      - createdb
  preparedDatabases:
    gitlabhq_production:
      owner: gitlab
      extensions:
        pg_trgm: public
        btree_gist: public

Is this possible?

[FxKu]

The latter seems more doable because PreparedDatabase is a struct whereas Databases is of type map[string]string. You could also GRANT gitlabhq_production_owner TO gitlab (I know, not from the manifest). Not sure if specifying an alternate owner should replace the default owner role or if that should still be there. Then there are also default privileges - for which owner roles should it be defined?

[weeix]

This would indeed increase flexibility for infrastructure automation. Currently, AFAIK, if one needs to choose the username and install extensions at the same time, they either have to:

• Define users and databases in the manifests, then manually run create extension <extension_name>; OR
• Define users and preparedDatabases in the manifests, then manually run grant <db_name>_owner to <username>;