Files
computer-playbook/roles/web-app-mediawiki/files/shell/composer_install_extension.sh
kevinveenbirkenbachandClaude Opus 5 575a5a87ac refactor(layout): sort shipped scripts by language and split the unit suite
Every script a role ships now lives under `files/<language>/`, and the unit
suite is split the same way: `tests/unit/python/` beside new sibling trees for
the other languages. `tests/lint/filesystem/test_role_files_layout.py` keeps it
that way; directories whose shape is dictated from outside carry a `.nocheck`
naming the constraint (Docker build contexts, WordPress mu-plugins, the Joomla
extension, Odoo addons, Playwright suites, the `files/test/test.sh` harness
that `test-e2e-cli` resolves generically).

This cannot be applied in halves. Moving a file and repointing what names it
are the same change: 14 references resolve only at deploy time, so the tree is
green either before or after, never between.

Those 14 were found by static resolution over every reference class, not by the
test suite -- a full `make quality-high` was green while all of them were
broken:

  * 7 `src:` values built from a role variable holding a bare filename
    (svc-bkp-remote-2-local, decidim, espocrm, friendica, joomla, pixelfed x2).
    The variable doubles as the destination name inside the container, so the
    language segment belongs at the call site, not in the variable.
  * `sys-service/tasks/04_base.yml` resolved every consumer's systemd script
    through `first_found(..., errors='strict')` over `files/script.{sh,py}`.
    18 roles ship exactly that and have no template fallback: the play would
    have died on each.
  * `sys-front-inj-javascript` fell back to `<role>/files/javascript.js`; the
    interface now reads `files/javascript/javascript.js`.
  * `sys-front-inj-logout/templates/head_sub.j2` built the cache-busting mtime
    path through `path_absolute(... 'files', ...)`.
  * 4 `ansible.builtin.script:` invocations naming a bare command
    (pull.py, prune.sh, set_postgres_superuser_password.sh, ganesha-serve.sh).
  * `dev-python/files/shell/install.sh` pointed at a sibling role's script.

Depth-dependent paths inside the moved trees were bumped accordingly: 59
`parents[N]` computations, 12 relative climbs, and the per-role recover CLI,
whose path `cli/administration/recover/recoverers.py` still assembled from the
pre-move location.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-22 01:31:09 +02:00

31 lines
1.2 KiB
Bash
Executable File

#!/usr/bin/env bash
#
# Run composer for one MediaWiki extension. Runs ON THE HOSTING NODE
# (delegated); copies install/helpers/ into the container and hands the work to
# composer_install.sh in there.
#
# The whole helper directory is copied rather than a list of names, so adding a
# helper means dropping a file into install/helpers/ and nothing else.
#
# Usage:
# composer_install_extension.sh MW_USER HTML_DIR EXT_NAME EXT_BRANCH
#
# Required env, supplied by the calling Ansible task:
# MW_CID resolved container id (resolve_host_cid), local to this node
# MEDIAWIKI_EXT_HELPER_DIR node-side directory holding the staged helpers
set -euo pipefail
MW_USER="$1"
HTML_DIR="$2"
EXT_NAME="$3"
EXT_BRANCH="$4"
CONTAINER="${MW_CID:?MW_CID env var (resolved container id) required}"
HELPER_DIR="${MEDIAWIKI_EXT_HELPER_DIR:?MEDIAWIKI_EXT_HELPER_DIR env var (staged helper directory) required}"
# nocheck: container-cp - the helpers are staged on the node this script runs on
container cp "${HELPER_DIR}/." "${CONTAINER}:/tmp/"
container exec -u "$MW_USER" "$CONTAINER" \
bash /tmp/composer_install.sh "${HTML_DIR}/extensions/${EXT_NAME}" "$EXT_BRANCH" "$EXT_NAME"