Timofei Larkin a24a581e53 fix(postgres): refuse account names CNPG must not get ...

The managed roles render on every path, while the refusals lived in
the init-script, which recovery does not render. A restore with an
older PostgreSQL could therefore hand CREATEROLE to a tenant user past
the version check, and nothing refused a user CloudNativePG or
PostgreSQL reserves, one named as a database's own role, or one whose
account name is no valid object name, which made the migration leave
the whole release out. The checks now render with the managed roles,
and the chart's account naming is pinned to the API's on one table of
names.

Assisted-by: LLM
Signed-off-by: Timofei Larkin <lllamnyp@gmail.com>

2026-10-27 16:31:03 +01:00

..

account_test.go

fix(postgres): refuse account names CNPG must not get

2026-10-27 16:31:03 +01:00

account.go

docs(api): cut comments to what the code cannot say

2026-10-26 10:54:40 +01:00