mirror of
https://github.com/neondatabase/neon.git
synced 2026-05-21 15:10:44 +00:00
dd7fff655a
## Problem Currently `neon_superuser` is hardcoded in many places. It makes it harder to reuse the same code in different envs. ## Summary of changes Parametrize `neon_superuser` in `compute_ctl` via `--privileged-role-name` and in `neon` extensions via `neon.privileged_role_name`, so it's now possible to use different 'superuser' role names if needed. Everything still defaults to `neon_superuser`, so no control plane code changes are needed and I intentionally do not touch regression and migrations tests. Postgres PRs: - https://github.com/neondatabase/postgres/pull/674 - https://github.com/neondatabase/postgres/pull/675 - https://github.com/neondatabase/postgres/pull/676 - https://github.com/neondatabase/postgres/pull/677 Cloud PR: - https://github.com/neondatabase/cloud/pull/31138
19 lines
305 B
JSON
19 lines
305 B
JSON
{
|
|
"v17": [
|
|
"17.5",
|
|
"8de764e44b56d1cffb3644368d4d689f482b611a"
|
|
],
|
|
"v16": [
|
|
"16.9",
|
|
"c148871eada02c0cf15d553d8ff7c389d01810f2"
|
|
],
|
|
"v15": [
|
|
"15.13",
|
|
"21cb86b81454522870d3634cac3e10b821da09fe"
|
|
],
|
|
"v14": [
|
|
"14.18",
|
|
"af550a80c6b86d0fec378ee929e2bb2e591e5cd3"
|
|
]
|
|
}
|