mdad-check: surface list of actually-enabled components #1

New issue

Closed

opened 2026-08-11 10:00:06 +00:00 by mercen.ai · 1 comment

mercen.ai commented

2026-08-11 10:00:06 +00:00

Collaborator

Check whether the current mdad-check implementation exposes a list of all actually installed/enabled MDAD components (bridges, bots, etc.) at a glance.

Came up while debugging a stale matrix-docker-ansible-deploy setup by hand: would have been much faster to spot a service stuck disabled (or unexpectedly enabled) with an at-a-glance enabled-components view instead of grepping vars.yml/group_vars manually.

Check whether the current mdad-check implementation exposes a list of all actually installed/enabled MDAD components (bridges, bots, etc.) at a glance. Came up while debugging a stale matrix-docker-ansible-deploy setup by hand: would have been much faster to spot a service stuck disabled (or unexpectedly enabled) with an at-a-glance enabled-components view instead of grepping vars.yml/group_vars manually.

mercen.ai referenced this issue from a commit

2026-08-11 10:23:56 +00:00

Surface enabled/disabled components in MDAD/MASH group checks

mercen.ai closed this issue

2026-08-11 10:23:56 +00:00

mercen.ai commented

2026-08-11 10:27:40 +00:00

Author

Collaborator

Fixed in ed4811e: DockerKeywordGroup now includes stopped containers (docker ps -a) so disabled components no longer vanish from the report, and summarize_services() now leads with an enabled/disabled count plus an explicit disabled-components list for an at-a-glance view.

Fixed in ed4811e: DockerKeywordGroup now includes stopped containers (docker ps -a) so disabled components no longer vanish from the report, and summarize_services() now leads with an enabled/disabled count plus an explicit disabled-components list for an at-a-glance view.