Benjamin LabrecqueandClaude Opus 5
430f99baa1
The ioc install/start/restart logic moves out of the ansible playbooks and the 'agebd ioc ...' cli into scripts run by the gitea runner: - ioc-install.sh / ioc-restart.sh run on the runner itself - ioc-start.sh triggers the shellbox commands over ssh - ioc-for-services.sh runs an action for one or all services They read the deployed ioc files from /sls instead of cloning the repo on the target host, so a service has to be deployed before its ioc can be installed. The deploy script therefore also takes over the environment suffix renaming of the subs/parameters files that ansible used to do, and the workflow steps are ordered deploy -> install. The commented-out ioc placeholders in the add-new-service workflow are filled in, and a manually triggered 'Ioc' workflow replaces the removed cli commands. With this, nothing uses ansible anymore, so the ansible dir, the cli ioc commands and the ansible dependencies are removed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PJTevZiSsHepW2xnJGQY49