update superlinter from known-vulnerable version

.github/workflows/lint-workflow.yml

@@ -44,6 +44,7 @@ jobs:
           # list of files that changed across commits
           fetch-depth: 0
           submodules: true
+          persist-credentials: false
 
       - name: Run ansible-lint
         uses: ansible/ansible-lint@e98f9b38769d45cbe3c55a23b2eb25631babe7c4 # v25.4.0
@@ -58,7 +59,7 @@ jobs:
         run: grep -v '^#' super-linter.env >> "$GITHUB_ENV"
 
       - name: Run super-linter
-        uses: super-linter/super-linter@4e8a7c2bf106c4c766c816b35ec612638dc9b6b2 # v7.3.0
+        uses: super-linter/super-linter/slim@9e863354e3ff62e0727d37183162c4a88873df41 # v8.6.0
         if: always()
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

README.md

@@ -108,7 +108,7 @@ The following system variables are provided by Azimuth:
 | `cluster_ssh_private_key_file`    | The path to a file containing the private key corresponding to `cluster_deploy_ssh_public_key`.<br>This is consumed by the `azimuth_cloud.terraform.infra` role.                                                                                                                                                                                                                                                         |
 | `cluster_network`                 | The name of the project internal network onto which cluster nodes should be placed.                                                                                                                                                                                                                                                                                                                                      |
 | `cluster_floating_network`        | The name of the floating network where floating IPs can be allocated.                                                                                                                                                                                                                                                                                                                                                    |
-| `cluster_upgrade_system_packages` | This variable is set when a PATCH operation is requested.<br>If given and `true`, it indicates that system packages should be upgraded. If not given, it should be assumed to be `false`.<br>The mechanism for acheiving this is appliance-specific, but it is expected to be a disruptive operation (e.g. rebuilding nodes).<br>If not given or set to `false`, disruptive operations should be avoided where possible. |
+| `cluster_upgrade_system_packages` | This variable is set when a PATCH operation is requested.<br>If given and `true`, it indicates that system packages should be upgraded. If not given, it should be assumed to be `false`.<br>The mechanism for achieving this is appliance-specific, but it is expected to be a disruptive operation (e.g. rebuilding nodes).<br>If not given or set to `false`, disruptive operations should be avoided where possible. |
 | `cluster_state`                   | This variable is set when a DELETE operation is requested.<br>If given and set to `absent` all cluster resources should be deleted, otherwise cluster resources should be updated as normal.                                                                                                                                                                                                                             |
 
 <!-- markdownlint-enable -->

super-linter.env

@@ -1,19 +1,31 @@
 # Exclude vendor submodules
 FILTER_REGEX_EXCLUDE=.*vendor/.*
 
-# Detect tha tthe default branch is main when running locally
+# Detect that default branch is main when running locally
 DEFAULT_BRANCH=main
 
 # Don't validate JSCPD
 VALIDATE_JSCPD=false
 
-# Don't validate JS standard because it conflicts with JS prettier
-VALIDATE_JAVASCRIPT_STANDARD=false
-
 # Don't validate Ansible because ansible-lint is more flexible
 VALIDATE_ANSIBLE=false
 
 # Don't validate YAML prettier because yamllint is sufficient
 VALIDATE_YAML_PRETTIER=false
 
+# Set to the default filename for yamllint
 YAML_CONFIG_FILE=.yamllint.yml
+
+VALIDATE_BIOME_FORMAT=false
+
+VALIDATE_BIOME_LINT=false
+
+VALIDATE_TRIVY=false
+
+# Only use ruff for python linting and formatting
+VALIDATE_PYTHON=false
+VALIDATE_PYTHON_BLACK=false
+VALIDATE_PYTHON_FLAKE8=false
+VALIDATE_PYTHON_ISORT=false
+VALIDATE_PYTHON_MYPY=false
+VALIDATE_PYTHON_PYLINT=false

ui-meta/sample-appliance.yml

@@ -43,7 +43,7 @@ parameters:
     #     The ID of an external IP in the target tenancy.
     #   cloud.volume_size
     #     An integer that represents the size of a volume that will be created.
-    #     Used for quota calcuations.
+    #     Used for quota calculations.
     #   cloud.volume
     #     The ID of a volume in the target tenancy.
     #   cloud.cluster