Add compliance workflow for PCO Prod3. (#373)

* Add compliance workflow for PCO Prod3.
  Using an application credential, because it's more elegant.
* Display results of v2 tests, which I expect Prod3 to pass.
* Consistent naming.
* Fix region of pco3 to read "prod3"
  Thanks to @mbuechse for spotting!

Signed-off-by: Kurt Garloff <[email protected]>

.github/scs-compliance-check/openstack/clouds.yaml

@@ -29,6 +29,14 @@ clouds:
     region_name: "prod2"
     interface: "public"
     identity_api_version: 3
+  pco-prod3:
+    auth_type: "v3applicationcredential"
+    auth:
+      auth_url: https://prod3.api.pco.get-cloud.io:5000
+      application_credential_id: "fe66c4c8cd3b4ea08262424783e1c58f"
+    region_name: "prod3"
+    interface: "public"
+    identity_api_version: 3
   wavestack:
     auth:
       auth_url: https://api.wavestack.de:5000

.github/workflows/check-pco-prod3-v1.yml

@@ -0,0 +1,23 @@
+name: "Compliance of pco-prod3"
+
+on:
+  # Trigger compliance check every day at 4:30 UTC
+  schedule:
+    - cron:  '30 4 * * *'
+  # Trigger compliance check after Docker image has been built
+  workflow_run:
+    workflows: [Build and publish scs-compliance-check Docker image]
+    types:
+      - completed
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+jobs:
+  check-pco-prod3:
+    uses: ./.github/workflows/scs-compliance-check-with-application-credential.yml
+    with:
+      version: v1
+      layer: iaas
+      cloud: "pco-prod3"
+      secret_name: "OS_PASSWORD_PCOPROD3"
+    secrets: inherit

.github/workflows/check-pco-prod3-v2.yml

@@ -0,0 +1,23 @@
+name: "Compliance of pco-prod3"
+
+on:
+  # Trigger compliance check every day at 4:30 UTC
+  schedule:
+    - cron:  '30 4 * * *'
+  # Trigger compliance check after Docker image has been built
+  workflow_run:
+    workflows: [Build and publish scs-compliance-check Docker image]
+    types:
+      - completed
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+jobs:
+  check-pco-prod3:
+    uses: ./.github/workflows/scs-compliance-check-with-application-credential.yml
+    with:
+      version: v2
+      layer: iaas
+      cloud: "pco-prod3"
+      secret_name: "OS_PASSWORD_PCOPROD3"
+    secrets: inherit

.github/workflows/check-pco-prod3-v3.yml

@@ -0,0 +1,23 @@
+name: "Compliance of pco-prod3"
+
+on:
+  # Trigger compliance check every day at 4:30 UTC
+  schedule:
+    - cron:  '30 4 * * *'
+  # Trigger compliance check after Docker image has been built
+  workflow_run:
+    workflows: [Build and publish scs-compliance-check Docker image]
+    types:
+      - completed
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+jobs:
+  check-pco-prod3:
+    uses: ./.github/workflows/scs-compliance-check-with-application-credential.yml
+    with:
+      version: v3
+      layer: iaas
+      cloud: "pco-prod3"
+      secret_name: "OS_PASSWORD_PCOPROD3"
+    secrets: inherit

README.md

@@ -11,6 +11,7 @@ This is a list of clouds that we test on a nightly basis against our `scs-compat
 | [gx-scs](https://github.com/SovereignCloudStack/docs/blob/main/community/cloud-resources/plusserver-gx-scs.md) | Dev environment provided for SCS & GAIA-X context | plusserver GmbH               | ![GitHub Workflow Status](https://img.shields.io/github/actions/workflow/status/SovereignCloudStack/standards/check-gx-scs-v1.yml?label=compliant)   |                                   [HM](https://health.gx-scs.sovereignit.cloud:3000/)                                    |
 | [pluscloud open - prod1](https://www.plusserver.com/en/products/pluscloud-open)                                | Public cloud for customers                        | plusserver GmbH               | ![GitHub Workflow Status](https://img.shields.io/github/actions/workflow/status/SovereignCloudStack/standards/check-pco-prod1-v1.yml?label=compliant) |                               [HM](https://health.prod1.plusserver.sovereignit.cloud:3000)                               |
 | [pluscloud open - prod2](https://www.plusserver.com/en/products/pluscloud-open)                                | Public cloud for customers                        | plusserver GmbH               | ![GitHub Workflow Status](https://img.shields.io/github/actions/workflow/status/SovereignCloudStack/standards/check-pco-prod2-v1.yml?label=compliant) |                               [HM](https://health.prod1.plusserver.sovereignit.cloud:3000)                               |
+| [pluscloud open - prod3](https://www.plusserver.com/en/products/pluscloud-open)                                | Public cloud for customers                        | plusserver GmbH               | ![GitHub Workflow Status](https://img.shields.io/github/actions/workflow/status/SovereignCloudStack/standards/check-pco-prod3-v2.yml?label=compliant) |                               [HM](https://health.prod1.plusserver.sovereignit.cloud:3000)                               |
 | [Wavestack](https://www.noris.de/wavestack-cloud/)                                                             | Public cloud for customers                        | noris network AG/Wavecon GmbH | ![GitHub Workflow Status](https://img.shields.io/github/actions/workflow/status/SovereignCloudStack/standards/check-wavestack-v3.yml?label=compliant) |                                 [HM](https://health.wavestack1.sovereignit.cloud:3000/)                                  |
 | [REGIO.cloud](https://regio.digital)                                                                           | Public cloud for customers                        | OSISM GmbH                    | ![GitHub Workflow Status](https://img.shields.io/github/actions/workflow/status/SovereignCloudStack/standards/check-regio-a-v3.yml?label=compliant)  | [Dashboard](https://apimon.services.regio.digital/public-dashboards/17cf094a47404398a5b8e35a4a3968d4?orgId=1&refresh=5m) |