Remove obsolete links to cloudalchemy roles in doc and comments

Author: elelaysh

ansible/filter_plugins/utils.py

@@ -12,7 +12,7 @@
 
 
 def prometheus_node_exporter_targets(hosts, hostvars, env_key, group):
-    """Return a mapping in cloudalchemy.nodeexporter prometheus_targets
+    """Return a mapping in prometheus.prometheus.prometheus prometheus_targets
     format.
 
     hosts: list of inventory_hostnames

docs/alerting.md

@@ -112,7 +112,7 @@ These are part of [Prometheus configuration](https://prometheus.io/docs/promethe
 which is defined for the appliance at
 [environments/common/inventory/group_vars/all/prometheus.yml](../environments/common/inventory/group_vars/all/prometheus.yml).
 
-Two [cloudalchemy.prometheus](https://github.com/cloudalchemy/ansible-prometheus)
+Two [prometheus.prometheus.prometheus](https://github.com/stackhpc/prometheus-community-ansible/tree/stackhpc/roles/prometheus)
 role variables are relevant:
 
 - `prometheus_alert_rules_files`: Paths to check for files providing rules.

docs/monitoring-and-logging.md

@@ -211,8 +211,10 @@ This section details the configuration of prometheus.
 
 ### Prometheus defaults
 
-Internally, we use the [cloudalchemy.prometheus](https://github.com/cloudalchemy/ansible-prometheus) role. You can customise any of the variables that the role supports. For a full list, please see the
-[upstream documentation](https://github.com/cloudalchemy/ansible-prometheus). The appliance defaults can be found here:
+Internally, we use the [prometheus](https://github.com/stackhpc/prometheus-community-ansible/tree/stackhpc/roles/prometheus) role
+from `prometheus-community/ansible`, lightly patched. You can customise any of the variables that the role supports. For a full list, please see the
+[upstream documentation](https://prometheus-community.github.io/ansible/branch/main/prometheus_role.html#ansible-collections-prometheus-prometheus-prometheus-role).
+The appliance defaults can be found here:
 
 > [environments/common/inventory/group_vars/all/prometheus.yml](../environments/common/inventory/group_vars/all/prometheus.yml)
 

docs/persistent-state.md

@@ -24,7 +24,7 @@ The `site` environment supports persistent state in the default OpenTofu (see `e
 
 **NB: The default OpenTofu is provided as a working example and for internal CI use - therefore this volume is deleted when running `tofu destroy` - this may not be appropriate for a production environment.**
 
-In general, the Prometheus data is likely to be the only sizeable state stored. The size of this can be influenced through [Prometheus role variables](https://github.com/cloudalchemy/ansible-prometheus#role-variables), e.g.:
+In general, the Prometheus data is likely to be the only sizeable state stored. The size of this can be influenced through [Prometheus role variables](https://prometheus-community.github.io/ansible/branch/main/prometheus_role.html#ansible-collections-prometheus-prometheus-prometheus-role), e.g.:
 
 - `prometheus_storage_retention` - [default](../environments/common/inventory/group_vars/all/prometheus.yml) 31d
 - `prometheus_storage_retention_size` - [default](../environments/common/inventory/group_vars/all/prometheus.yml) 100GB

environments/common/inventory/group_vars/all/prometheus.yml

@@ -17,7 +17,7 @@ prometheus_alertmanager_config_default:
           - "{{ alertmanager_address }}:{{ alertmanager_port }}"
     basic_auth:
       username: alertmanager
-      # cloudalchemy.prometheus/preflight checks this config so it must be
+      # prometheus.prometheus.prometheus/preflight checks this config so it must be
       # templatable even during build when it is not used
       password: "{{ vault_alertmanager_admin_password | default('UNDEFINED') }}"