We had some discussion via chat about this, in particular a couple concerns with templates:

• Escaping input within the templates
• syntax highlighting within the script (naming things script.sh.tpl works with vscode, this varies by editor tho)

Our current plan is to make a MR with the templates version and discuss further.

If we end up disliking the templated version, we can always switch back to the bare scripts.

jnuche opened https://gitlab.wikimedia.org/repos/qte/catalyst/ci-charts/-/merge_requests/16

add provisioning shell scripts from Patchdemo

jnuche updated https://gitlab.wikimedia.org/repos/qte/catalyst/ci-charts/-/merge_requests/16

add provisioning shell scripts from Patchdemo

jnuche merged https://gitlab.wikimedia.org/repos/qte/catalyst/ci-charts/-/merge_requests/16

add provisioning shell scripts from Patchdemo

jnuche opened https://gitlab.wikimedia.org/repos/qte/catalyst/ci-charts/-/merge_requests/17

mw.yaml: use bookworm to run the wiki init container

kindrobot closed https://gitlab.wikimedia.org/repos/qte/catalyst/ci-charts/-/merge_requests/17

Draft: mw.yaml: use bookworm to run the wiki init container

Good learning from this task: PatchDemo previously ran on the same machine as all of the development environments and so it was ideal to use the same PHP version + Node version + Debian version as was needed for the development environments. In our Kubernetes future, the needs of PatchDemo can be separated from the needs of the environments.

Followup work here is to adapt the development environment provisioning in catalyst for packages.json to work on buster.