[GAT] Backup Cleanup Bump gxadmin ansible role to 0.0.14

topics/admin/tutorials/apptainer/tutorial.md

@@ -105,7 +105,7 @@ First, we will install Apptainer using Ansible. Since there is a package availab
 >    ```diff
 >    --- a/requirements.yml
 >    +++ b/requirements.yml
->    @@ -20,3 +20,6 @@
+>    @@ -19,3 +19,6 @@
 >     # CVMFS Support
 >     - src: galaxyproject.cvmfs
 >       version: 0.3.1

topics/admin/tutorials/backup-cleanup/tutorial.md

@@ -83,7 +83,7 @@ tutorial]({% link topics/admin/tutorials/gxadmin/tutorial.md %}).
 >       version: 0.1.11
 >    +# gxadmin (used in cleanup, and later monitoring.)
 >    +- src: galaxyproject.gxadmin
->    +  version: 0.0.12
+>    +  version: 0.0.14
 >    {% endraw %}
 >    ```
 >    {: data-commit="Add requirement"}

topics/admin/tutorials/beacon/tutorial.md

@@ -92,7 +92,7 @@ This tutorial will guide you through setting up a [GA4GH Beacon](https://beacon-
 >    ```diff
 >    --- a/requirements.yml
 >    +++ b/requirements.yml
->    @@ -60,3 +60,8 @@
+>    @@ -59,3 +59,8 @@
 >     # Our FTP Server
 >     - src: galaxyproject.proftpd
 >       version: 0.3.1

topics/admin/tutorials/celery/tutorial.md

@@ -109,7 +109,7 @@ First we need to add our new Ansible Roles to the `requirements.yml`:
 >    ```diff
 >    --- a/requirements.yml
 >    +++ b/requirements.yml
->    @@ -38,3 +38,8 @@
+>    @@ -37,3 +37,8 @@
 >       version: 1.4.4
 >     - src: galaxyproject.pulsar
 >       version: 1.0.10

topics/admin/tutorials/connect-to-compute-cluster/tutorial.md

@@ -100,7 +100,7 @@ be taken into consideration when choosing where to run jobs and what parameters
 >    ```diff
 >    --- a/requirements.yml
 >    +++ b/requirements.yml
->    @@ -23,3 +23,8 @@
+>    @@ -22,3 +22,8 @@
 >     # Singularity/Apptainer
 >     - src: usegalaxy_eu.apptainer
 >       version: 0.0.3

topics/admin/tutorials/cvmfs/tutorial.md

@@ -193,8 +193,8 @@ If the terms "Ansible", "role" and "playbook" mean nothing to you, please checko
 >    ```diff
 >    --- a/requirements.yml
 >    +++ b/requirements.yml
->    @@ -17,3 +17,6 @@
->     # TUS (uploads)
+>    @@ -16,3 +16,6 @@
+>       version: 0.0.14
 >     - name: galaxyproject.tusd
 >       version: 0.0.1
 >    +# CVMFS Support

topics/admin/tutorials/ftp/tutorial.md

@@ -85,7 +85,7 @@ If the terms "Ansible", "role" and "playbook" mean nothing to you, please checko
 >    ```diff
 >    --- a/requirements.yml
 >    +++ b/requirements.yml
->    @@ -57,3 +57,6 @@
+>    @@ -56,3 +56,6 @@
 >     # Sentry
 >     - name: mvdbeek.sentry_selfhosted
 >       src: https://github.com/mvdbeek/ansible-role-sentry/archive/main.tar.gz

topics/admin/tutorials/job-destinations/tutorial.md

@@ -182,7 +182,7 @@ And of course, Galaxy has an Ansible Role for that.
 >    ```diff
 >    --- a/requirements.yml
 >    +++ b/requirements.yml
->    @@ -28,3 +28,6 @@
+>    @@ -27,3 +27,6 @@
 >       version: 0.0.3
 >     - src: galaxyproject.slurm
 >       version: 1.0.2

topics/admin/tutorials/monitoring/tutorial.md

@@ -90,7 +90,7 @@ The available Ansible roles for InfluxDB unfortunately do not support configurin
 >    ```diff
 >    --- a/requirements.yml
 >    +++ b/requirements.yml
->    @@ -43,3 +43,5 @@
+>    @@ -42,3 +42,5 @@
 >       version: 1.8.0
 >     - name: usegalaxy_eu.flower
 >       version: 1.0.2
@@ -296,7 +296,7 @@ Setting up Telegraf is again very simple. We just add a single role to our playb
 >    ```diff
 >    --- a/requirements.yml
 >    +++ b/requirements.yml
->    @@ -45,3 +45,7 @@
+>    @@ -44,3 +44,7 @@
 >       version: 1.0.2
 >     - src: usegalaxy_eu.influxdb
 >       version: v6.0.7
@@ -458,7 +458,7 @@ There are some nice examples of dashboards available from the public Galaxies, w
 >    ```diff
 >    --- a/requirements.yml
 >    +++ b/requirements.yml
->    @@ -49,3 +49,5 @@
+>    @@ -48,3 +48,5 @@
 >     - name: dj-wasabi.telegraf
 >       src: https://github.com/dj-wasabi/ansible-telegraf
 >       version: 6f6fdf7f5ead491560783d52528b79e9e088bd5b

topics/admin/tutorials/pulsar/tutorial.md

@@ -164,7 +164,7 @@ Firstly we will add and configure another *role* to our Galaxy playbook - a comm
 >    ```diff
 >    --- a/requirements.yml
 >    +++ b/requirements.yml
->    @@ -31,3 +31,10 @@
+>    @@ -30,3 +30,10 @@
 >     # TPV Linting
 >     - name: usegalaxy_eu.tpv_auto_lint
 >       version: 0.4.3

topics/admin/tutorials/sentry/tutorial.md

@@ -67,7 +67,7 @@ First we need to add our new Ansible role to `requirements.yml`:
 >    ```diff
 >    --- a/requirements.yml
 >    +++ b/requirements.yml
->    @@ -54,3 +54,6 @@
+>    @@ -53,3 +53,6 @@
 >     # Training Infrastructure as a Service
 >     - src: galaxyproject.tiaas2
 >       version: 2.1.5

topics/admin/tutorials/tiaas/tutorial.md

@@ -75,7 +75,7 @@ This tutorial will go cover how to set up such a service on your own Galaxy serv
 >    ```diff
 >    --- a/requirements.yml
 >    +++ b/requirements.yml
->    @@ -51,3 +51,6 @@
+>    @@ -50,3 +50,6 @@
 >       version: 6f6fdf7f5ead491560783d52528b79e9e088bd5b
 >     - src: cloudalchemy.grafana
 >       version: 0.14.2

topics/admin/tutorials/tus/tutorial.md

@@ -63,11 +63,10 @@ To allow your user to upload via TUS, you will need to:
 >    ```diff
 >    --- a/requirements.yml
 >    +++ b/requirements.yml
->    @@ -14,3 +14,6 @@
+>    @@ -14,3 +14,5 @@
 >     # gxadmin (used in cleanup, and later monitoring.)
 >     - src: galaxyproject.gxadmin
->       version: 0.0.12
->    +# TUS (uploads)
+>       version: 0.0.14
 >    +- name: galaxyproject.tusd
 >    +  version: 0.0.1
 >    {% endraw %}