The provisioner on soliplex-concierge¶
Part of Upgrading an existing stack.
Walk this rung with the v0.21 skill release —
its generator produces the rung's end state. The stack being upgraded names
the release that generated it in its own [tool.soliplex-template] manifest —
use that one when climbing from an older shape.
This rung changes no releases: soliplex, haiku.rag-slim and the web client
stay where rung 7 left them. It moves the room provisioner onto
soliplex-concierge's provisioner framework, which soliplex-template 0.21
depends on (soliplex-concierge[provisioner] >= 0.14). What changes:
- the
soliplex-provisionerservice runs a new factory,soliplex_template.provisioner.wiring:create_app stack-init's provisioner step imports from the newsoliplex_template.provisionerpackage- the backend's environment, which
soliplex-dev,soliplex-provisionerandstack-initshare, setsSOLIPLEX_INSTALLATION_PATH, sosoliplex-clicommands no longer need the installation's path - each room provisioned from now on records its request and its policy in
the provisioned-rooms clone (
provision.yaml,authz.yaml), andsoliplex-provision-room --reconcilereplays them (see Room provisioning) - in a stack with the concierge, reinstallint the about room enables the new provisioning features (see Rooms for someone else)
The old factory (soliplex_template.provision_service:create_app) and
stack-init's old import still work in soliplex-template 0.21, so a stack
that skips steps 3 and 4 keeps running. They are deprecated, and go in a
later release.
Where a step differs, it says which kind of stack it means:
- a stack with the concierge has a
soliplex-conciergeline inbackend/requirements.txt, and anabout-<project>room - a stack without the concierge has neither
Skip the steps that do not apply. Each names what the current template has; compare against a stack the rung's release generates.
-
Stop the stack with
docker compose down. This rung changes no database, so no backup is needed beyond your usual one. -
In a stack with the concierge, raise its pin to 0.14. In
backend/requirements.txt, change thesoliplex-conciergeline's version to0.14(for examplesoliplex-concierge[truststore]==0.14).soliplex-devinstallssoliplex-template0.21 with the backend image's versions as constraints, so an older concierge pin makes its build fail. -
Run the new provisioner factory. In
docker-compose.yml, in thesoliplex-provisionerservice'scommand:replacing
soliplex_template.provision_service:create_app. -
Update
stack-init's provisioner step. Instack-init/init.d/20-provisioner-admin.py, replacefrom soliplex_template import provisionwith:and
provision.DEFAULT_SERVICE_SUBJECTwithadapters.DEFAULT_SERVICE_SUBJECT. -
Set the installation path. In
docker-compose.yml, add to thebackendservice'senvironment(the&backend_environmentblock), afterPYTHONPATH: -
Install
soliplex-template0.21 insoliplex-dev. Insoliplex-dev/Dockerfile, change theSOLIPLEX_TEMPLATEdefault: -
Rebuild, run
stack-init, then start. The backend image rebuilds in a stack with the concierge, for its new pin;soliplex-devandsoliplex-provisionerrebuild in every stack: -
In a stack with the concierge, reinstall the about room with the
soliplex-concierge-installerskill from soliplex-concierge'sv0.14release (installer 0.7.0 or later), passing--forceand the Gitea owner and repository you installed it with. Its prompt now lets an admin request a room for someone else.--forcereplaces the room's files: comparegit diffbefore you commit, and carry over any edits of your own. The reinstalledroom_config.yamlstarts with an# Installed by soliplex-concierge-installer <version>line. -
Reconcile, to see where the clone stands. Rooms provisioned before this rung have no
authz.yaml; reconcile names them and leaves their policies alone: -
Then check that the provisioner service answers (
GET /okthrough the compose network, ordocker compose ps soliplex-provisionerreporting it healthy).Commit.