docker_systemd_service

History

Bertrand Lanson ffbb6157ef All checks were successful test / Retrieve Credentials (pull_request) Successful in 2s Details development / Check commit compliance (push) Successful in 5s Details pull-requests-open / Check commit compliance (pull_request) Successful in 5s Details test / end_to_end_role (default, debian11) (pull_request) Successful in 39s Details test / end_to_end_role (default, debian12) (pull_request) Successful in 40s Details test / end_to_end_role (default, ubuntu2004) (pull_request) Successful in 40s Details test / end_to_end_role (default, ubuntu2204) (pull_request) Successful in 39s Details test / end_to_end_role (with_custom_flags, debian11) (pull_request) Successful in 37s Details test / end_to_end_role (default, ubuntu2404) (pull_request) Successful in 39s Details test / end_to_end_role (with_custom_flags, ubuntu2204) (pull_request) Successful in 38s Details test / end_to_end_role (with_custom_flags, debian12) (pull_request) Successful in 39s Details test / end_to_end_role (with_custom_flags, ubuntu2004) (pull_request) Successful in 39s Details test / end_to_end_role (with_custom_flags, ubuntu2404) (pull_request) Successful in 38s Details feat: only allow starting and managing running services. destroying/removing services should be handled separately, most likely by the end user's custom code, to avoid data loss, etc...		2024-11-09 13:24:14 +01:00
..
all.yml	feat: only allow starting and managing running services.	2024-11-09 13:24:14 +01:00