Files
computer-playbook/roles/sys-svc-engine/tasks/provision.yml
kevinveenbirkenbachandClaude Opus 4.8 131231ee28 fix(loader): stop consumer compose_mode_force from leaking into lazy providers
web-app-matrix forces compose mode for its own ansible flavor; when it
was the first consumer to lazy-load the object-store provider, the
include_role inherited that override and web-app-seaweedfs came up via
compose up instead of docker stack deploy, so seaweedfs_seaweedfs never
existed and the next consumer's bucket provisioning died on
resolve-container-id. Neutralize compose_mode_force on the lazy
provider includes of sys-svc-objstore and sys-svc-engine, matching the
neutralization sys-svc-rdbms already carries.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-15 16:07:39 +02:00

28 lines
987 B
YAML

---
- name: "🔧 Provision '{{ _engine_consumer_id }}' on '{{ _engine_provider_role }}'"
vars:
_engine_provider_role: "svc-db-{{ _engine_type }}"
block:
- name: "🧩 Load engine provider '{{ _engine_provider_role }}' (lazy)"
ansible.builtin.include_role:
name: "{{ _engine_provider_role }}"
vars:
application_id: "{{ _engine_provider_role }}"
compose_mode_force: ""
when: >-
lookup(
'vars',
'run_once_' ~ (_engine_provider_role | replace('-', '_')),
default='__missing__'
) == '__missing__'
- name: "🎬 Initialize '{{ _engine_consumer_id }}' on '{{ _engine_provider_role }}'"
ansible.builtin.include_role:
name: "{{ _engine_provider_role }}"
vars:
application_id: "{{ _engine_provider_role }}"
database_init: true
database_consumer_id: "{{ _engine_consumer_id }}"
compose_repository_pull: false
compose_mode_force: ""