Version 1.15.0 is released

Changes

• feat: New credentials.templates feature that will replace secretsTemplates soon | Improve secrets and confimaps templating #48
• build: Test against Postgres 16 | build: Start testing against postgres 16 #58
• feat(Postgres): Set and Revoke default privileges by the database owner | Set and revoke default priveleges by the DB owner #56
• refactor: Remove the broken MySQL test | Fix the test for MySQL handler #55

Notes

secretsTemplates are considered deprecated since this version, so we suggest migrating to new credentials.temlates feature. The documentation can be found here.
The new templater will let you use Secrets and ConfigMaps directly, so the templating is a way more flexible.
For example

spec:
  credentials:
    templates:
      - name: PASSWORD
        template: "{{ .Secret \"POSTGRES_PASSWORD\" }}"
        secret: true
      - name: DATABASE
        template: "{{ .ConfigMap \"POSTGRES_DATABASE\" }}"
        secret: false

Fields that were available in secretsTemplates still can be accessed via helpers.

So instead of

spec:
  secretsTemplates:
    CONNECTION_STRING: "jdbc:{{ .Protocol }}://{{ .UserName }}:{{ .Password }}@{{ .DatabaseHost }}:{{ .DatabasePort }}/{{ .DatabaseName }}" 

now it's:

spec:
  credentials:
    templates:
      - name: CONNECTION_STRING
        template: "jdbc:{{ .Protocol }}://{{ .Username }}:{{ .Password }}@{{ .Hostname }}:{{ .Port }}/{{ .Database }}"
        secret: true

Also, it's possible to query data directly from a Database, for example:

spec:
  credentials:
    templates:
      - name: POSTGRES_VERSION
        secret: false
        template: "{{ .Query \"SHOW server_version;\" }}"

In the following API version, secretsTemplates will be removed, and there will be a conversion webhook for turning them into credentials.templates.