[DPE-10887] refactor(relations): adopt the single-kernel client relation - #1900
Draft
marceloneppel wants to merge 3 commits into
Draft
[DPE-10887] refactor(relations): adopt the single-kernel client relation#1900marceloneppel wants to merge 3 commits into
marceloneppel wants to merge 3 commits into
Conversation
marceloneppel
force-pushed
the
skl-02-adopt-database-provider
branch
from
August 17, 2026 19:47
6ddf535 to
f18998d
Compare
github-actions
Bot
added
the
Libraries: Out of sync
marceloneppel
force-pushed
the
skl-01-adopt-update-config
branch
2 times, most recently
from
August 18, 2026 21:20
43dac9e to
429abf3
Compare
marceloneppel
force-pushed
the
skl-02-adopt-database-provider
branch
from
August 18, 2026 21:34
b7e5521 to
2ee2329
Compare
marceloneppel
added
the
not bug or enhancement
This was referenced Aug 20, 2026
marceloneppel
changed the title
Migrate the charm's update_config, resource introspection, and TLS reload onto the single-kernel library, now published as 16.3.5: the charm delegates Patroni config re-render to the lib's ConfigManager, reads available resources through the lib, and observes the lib's tls_files_pushed event for the TLS reload bridge. Drops the charm's now-redundant patroni.yml.j2 template and update_config tests. The pin moves from the pre-merge archive-URL SHA to the published 16.3.5 release (extras: postgresql, vm) -- same lib tree, now sourced from PyPI; the adoption code is unchanged. Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com>
Move the database (client) relation provider into the single-kernel library: delete the charm's src/relations/postgresql_provider.py and its tests, and wire the provider events through the lib's DatabaseManager. The charm implements get_resource_provider so the lib's ConfigManager reads substrate resources via the resource_provider injection contract (lib #215) on the db-provider lib branch. Pin the lib at the rebased test/02-db-events tip (archive-URL SHA, since the db-provider stack is not yet published to PyPI), stacked on the skl-01 16.3.5 update_config adoption. Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com>
marceloneppel
force-pushed
the
skl-02-adopt-database-provider
branch
from
August 20, 2026 18:00
72954e6 to
90720c8
Compare
The pinned archive moves from 335f89b to 41009a8 so the charm picks up the port review's rework: all status writes now route through the refresh-gated set_unit_status, K8s keeps its whole-relation endpoint refresh and its own defer wording, the user hash freezes per hook, the failed-init blocking message converges on the clearer wording with the unblock substring widened to match, and the lib version advances to 16.3.6 so the release ships the complete database subsystem. Signed-off-by: Marcelo Henrique Neppel <marcelo.neppel@canonical.com>
marceloneppel
force-pushed
the
skl-02-adopt-database-provider
branch
from
August 20, 2026 20:09
90720c8 to
065e94d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue
src/relations/postgresql_provider.py(645 lines) is a near-copy of the K8s charm's version of the same file, and the library now owns the postgresql-client relation. Keeping both means two implementations of one databag contract drifting apart — which is where the doubled-port read-only URI the library fixes came from.Solution
Deletes the charm's provider and its tests, and constructs
single_kernel_postgresql.events.database.DatabaseEventsHandlerinstead. The remaining call sites move to the manager it builds:oversee_users()now takes the PostgreSQL client,update_endpoints()takes an optional relation id rather than an event.Two seams close with it:
refresh_endpointsis gone.ConfigManagerholds the database manager and refreshes endpoints itself.update_configno longer takes a user hash._collect_user_relationsdelegates to the manager, and the hash is derived from the same relation data the user-databases map comes from, sogenerate_user_hashhad nothing left to do.relations_user_databases_mapstays here — its computation diverges between the substrates and belongs to the core event-loop phase.Behaviour is unchanged on this substrate. The library keeps VM's
relation-<id>role names, its Patroni-member endpoint derivation, itscreatedbextra-user-role allowance, and itsPostgreSQLBaseErrorcatch, all substrate-gated.Checklist