refactor: remove already deprecated azure-vault distributions

.github/workflows/deployment-test.yaml

@@ -27,20 +27,6 @@ on:
   workflow_dispatch:
 
 jobs:
-  secret-presence:
-    runs-on: ubuntu-latest
-    outputs:
-      AZURE_KV_CREDS: ${{ steps.secret-presence.outputs.AZURE_KV_CREDS }}
-    steps:
-      - name: Check whether secrets exist
-        id: secret-presence
-        run: |
-          [ ! -z "${{ secrets.AZURE_TENANT_ID }}" ] && 
-          [ ! -z "${{ secrets.AZURE_CLIENT_ID }}" ] && 
-          [ ! -z "${{ secrets.AZURE_CLIENT_SECRET }}" ] && 
-          [ ! -z "${{ secrets.AZURE_VAULT_NAME }}" ]  && 
-          echo "AZURE_KV_CREDS=true" >> $GITHUB_OUTPUT
-          exit 0
 
   test-prepare:
     runs-on: ubuntu-latest

.github/workflows/trigger-docker-publish.yaml

@@ -55,8 +55,6 @@ jobs:
       matrix:
         variant: [ { dir: edc-controlplane, img: edc-runtime-memory },
                    { dir: edc-controlplane, img: edc-controlplane-postgresql-hashicorp-vault },
-                   { dir: edc-controlplane, img: edc-controlplane-postgresql-azure-vault },
-                   { dir: edc-dataplane,    img: edc-dataplane-azure-vault },
                    { dir: edc-dataplane,    img: edc-dataplane-hashicorp-vault },
                    { dir: edc-tests/runtime, img: mock-connector }]
     permissions:

.github/workflows/trivy.yml

@@ -85,9 +85,7 @@ jobs:
       matrix:
         image:
           - edc-runtime-memory
-          - edc-controlplane-postgresql-azure-vault
           - edc-controlplane-postgresql-hashicorp-vault
-          - edc-dataplane-azure-vault
           - edc-dataplane-hashicorp-vault
     steps:
       - uses: actions/checkout@v4

DEPENDENCIES

@@ -6,15 +6,12 @@ maven/mavencentral/com.apicatalog/iron-verifiable-credentials/0.14.0, Apache-2.0
 maven/mavencentral/com.apicatalog/titanium-json-ld/1.0.0, Apache-2.0, approved, clearlydefined
 maven/mavencentral/com.apicatalog/titanium-json-ld/1.4.0, Apache-2.0, approved, #15200
 maven/mavencentral/com.apicatalog/titanium-json-ld/1.4.1, Apache-2.0, approved, #15200
-maven/mavencentral/com.azure/azure-core-http-netty/1.15.5, MIT AND Apache-2.0, approved, #16697
 maven/mavencentral/com.azure/azure-core-http-netty/1.15.6, MIT AND Apache-2.0, approved, #16697
 maven/mavencentral/com.azure/azure-core-http-netty/1.15.7, MIT AND Apache-2.0, approved, #16697
-maven/mavencentral/com.azure/azure-core/1.53.0, MIT, approved, clearlydefined
 maven/mavencentral/com.azure/azure-core/1.54.0, MIT, approved, clearlydefined
 maven/mavencentral/com.azure/azure-core/1.54.1, MIT, approved, clearlydefined
 maven/mavencentral/com.azure/azure-identity/1.14.2, MIT, approved, #16714
 maven/mavencentral/com.azure/azure-json/1.3.0, MIT, approved, clearlydefined
-maven/mavencentral/com.azure/azure-security-keyvault-secrets/4.9.0, MIT, approved, #16850
 maven/mavencentral/com.azure/azure-storage-blob/12.29.0, MIT, approved, #17273
 maven/mavencentral/com.azure/azure-storage-common/12.28.0, MIT, approved, #17275
 maven/mavencentral/com.azure/azure-storage-internal-avro/12.14.0, MIT, approved, #17274
@@ -326,7 +323,6 @@ maven/mavencentral/org.eclipse.edc.aws/validator-data-address-s3/0.11.0-20241127
 maven/mavencentral/org.eclipse.edc.azure/azure-blob-core/0.11.0-20241127-SNAPSHOT, Apache-2.0, approved, technology.edc
 maven/mavencentral/org.eclipse.edc.azure/data-plane-azure-storage/0.11.0-20241127-SNAPSHOT, Apache-2.0, approved, technology.edc
 maven/mavencentral/org.eclipse.edc.azure/provision-blob/0.11.0-20241127-SNAPSHOT, Apache-2.0, approved, technology.edc
-maven/mavencentral/org.eclipse.edc.azure/vault-azure/0.11.0-20241127-SNAPSHOT, Apache-2.0, approved, technology.edc
 maven/mavencentral/org.eclipse.edc/accesstoken-lib/0.11.0-20241127-SNAPSHOT, Apache-2.0, approved, technology.edc
 maven/mavencentral/org.eclipse.edc/accesstokendata-store-sql/0.11.0-20241127-SNAPSHOT, Apache-2.0, approved, technology.edc
 maven/mavencentral/org.eclipse.edc/api-core/0.11.0-20241127-SNAPSHOT, Apache-2.0, approved, technology.edc

README.md

@@ -28,20 +28,15 @@ The eclipse data space connector is split up into Control-Plane and Data-Plane,
 administration layer and has responsibility of resource management, contract negotiation and administer data transfer.
 The Data-Plane does the heavy lifting of transferring and receiving data streams.
 
-Depending on your environment there are different derivatives of the control-plane prepared:
+Control-Plane distribution:
 
-- [edc-controlplane-postgresql-azure-vault](edc-controlplane/edc-controlplane-postgresql-azure-vault) with dependency onto
-  - [Azure Key Vault](https://azure.microsoft.com/en-us/services/key-vault/#product-overview)
-  - [PostgreSQL 8.2 or newer](https://www.postgresql.org/)
 - [edc-controlplane-postgresql-hashicorp-vault](edc-controlplane/edc-controlplane-postgresql-hashicorp-vault) with
   dependency onto
   - [Hashicorp Vault](https://www.vaultproject.io/)
   - [PostgreSQL 8.2 or newer](https://www.postgresql.org/)
 
-Derivatives of the Data-Plane can be found here
+Data-Plane distribution:
 
-- [edc-dataplane-azure-vault](edc-dataplane/edc-dataplane-azure-vault) with dependency onto
-  - [Azure Key Vault](https://azure.microsoft.com/en-us/services/key-vault/#product-overview)
 - [edc-dataplane-hashicorp-vault](edc-dataplane/edc-dataplane-hashicorp-vault) with dependency onto
   - [Hashicorp Vault](https://www.vaultproject.io/)