Skip to content

feat: remove pgedge_application built-in roles #365

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rshoemaker merged 1 commit into from
Apr 24, 2026
Merged

feat: remove pgedge_application built-in roles #365

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions docs/development/running-locally.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -106,8 +106,7 @@ cp1-req create-database '{
{
"username": "app",
"password": "password",
"attributes": ["LOGIN"],
"roles": ["pgedge_application"]
"attributes": ["LOGIN"]
}
],
"nodes": [
Expand All @@ -133,8 +132,7 @@ restish control-plane-local-1 create-database '{
{
"username": "app",
"password": "password",
"attributes": ["LOGIN"],
"roles": ["pgedge_application"]
"attributes": ["LOGIN"]
}
],
"nodes": [
Expand Down
278 changes: 0 additions & 278 deletions docs/development/service-credentials.md
View file
Open in desktop

This file was deleted.

12 changes: 3 additions & 9 deletions docs/development/supported-services.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -278,8 +278,7 @@ read-only access to the `public` schema. Credentials are persisted in the
resource state and reused on subsequent reconciliation cycles. The role is
created on the primary instance and Spock replicates it to all other nodes
automatically. On `Delete`, it drops the role. Runs on
`PrimaryExecutor(nodeName)`. See `docs/development/service-credentials.md` for
full details on credential generation.
`PrimaryExecutor(nodeName)`.

**DirResource** (`server/internal/filesystem/dir_resource.go`): Creates and
manages a host-side directory for the service instance's data files. The
Expand Down Expand Up @@ -686,8 +685,7 @@ name is `"{databaseID}-database"` (set in the `Network.Name` field in

Usernames longer than 63 characters are truncated with a deterministic hash
suffix. Because the username is now per-service (not per-instance), all
instances of the same service share one set of credentials. See
`docs/development/service-credentials.md` for details.
instances of the same service share one set of credentials.

### ServiceResources

Expand Down Expand Up @@ -1109,11 +1107,7 @@ The following are service-type-agnostic and require no modification:

## Future Work

- **Read/write service user accounts**: Service users are currently provisioned
with the `pgedge_application_read_only` role. Some service types will require
write access (`INSERT`, `UPDATE`, `DELETE`, DDL). This will require a
mechanism for the service spec to declare the required access level and for
`ServiceUserRole` to provision the appropriate role accordingly.

- **Primary-aware database connection routing** *(in progress — PLAT-463)*:
`BuildServiceHostList` and `resolveTargetSessionAttrs` provide multi-host
connection topology with `target_session_attrs` support. Services receive an
Expand Down
Loading