[
https://issues.apache.org/jira/browse/CAMEL-26617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-26617:
-------------------------------------
Description:
Builds on the Floci AZ container that CAMEL-26615 adds to
{{camel-test-infra-azure-common}}.
The integration tests of camel-azure-key-vault ({{KeyVaultOperationsTest}} in
the integration package, {{KeyVaultPropertiesSourceNoEnvTestIT}}) need a real
vault and a service principal ({{vaultName}}, {{clientId}}, {{clientSecret}},
{{tenantId}}).
Floci AZ emulates the Key Vault secrets API (create, get, versions, properties,
soft delete, recover, purge) on {{/devstoreaccount1-keyvault}}. The Java SDK
enforces HTTPS and challenge-based authentication, so the client needs a token
credential, TLS (or a policy that rewrites the scheme) and
{{disableChallengeResourceVerification()}}.
h4. Change
* Add a {{camel-test-infra-azure-key-vault}} module that starts Floci AZ and
builds a {{SecretClient}} for it.
* Run the producer operations (createSecret, getSecret, deleteSecret,
purgeDeletedSecret and the others) against it through the {{secretClient}}
option; keep the remote mode.
* Skip the integration tests on ppc64le and s390x.
h4. Not covered
The {{azure:}} properties function always builds
{{https://<vaultName>.vault.azure.net}}, so
{{KeyVaultPropertiesSourceNoEnvTestIT}} stays remote only. Pointing the
function at another endpoint would be a component change of its own.
Depends on CAMEL-26615.
_Claude Code on behalf of Andrea Cosentino_
was:
Part of the move of the Azure test-infra to Floci AZ (CAMEL-26613).
The integration tests of camel-azure-key-vault ({{KeyVaultOperationsTest}} in
the integration package, {{KeyVaultPropertiesSourceNoEnvTestIT}}) need a real
vault and a service principal ({{vaultName}}, {{clientId}}, {{clientSecret}},
{{tenantId}}).
Floci AZ emulates the Key Vault secrets API (create, get, versions, properties,
soft delete, recover, purge) on {{/devstoreaccount1-keyvault}}. The Java SDK
enforces HTTPS and challenge-based authentication, so the client needs a token
credential, TLS (or a policy that rewrites the scheme) and
{{disableChallengeResourceVerification()}}.
h4. Change
* Add a {{camel-test-infra-azure-key-vault}} module that starts Floci AZ and
builds a {{SecretClient}} for it.
* Run the producer operations (createSecret, getSecret, deleteSecret,
purgeDeletedSecret and the others) against it through the {{secretClient}}
option; keep the remote mode.
* Skip the integration tests on ppc64le and s390x.
h4. Not covered
The {{azure:}} properties function always builds
{{https://<vaultName>.vault.azure.net}}, so
{{KeyVaultPropertiesSourceNoEnvTestIT}} stays remote only. Pointing the
function at another endpoint would be a component change of its own.
Depends on CAMEL-26613.
_Claude Code on behalf of Andrea Cosentino_
> camel-azure-key-vault - run the integration tests on Floci AZ
> -------------------------------------------------------------
>
> Key: CAMEL-26617
> URL: https://issues.apache.org/jira/browse/CAMEL-26617
> Project: Camel
> Issue Type: Test
> Components: camel-azure
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 4.24.0
>
>
> Builds on the Floci AZ container that CAMEL-26615 adds to
> {{camel-test-infra-azure-common}}.
> The integration tests of camel-azure-key-vault ({{KeyVaultOperationsTest}} in
> the integration package, {{KeyVaultPropertiesSourceNoEnvTestIT}}) need a real
> vault and a service principal ({{vaultName}}, {{clientId}}, {{clientSecret}},
> {{tenantId}}).
> Floci AZ emulates the Key Vault secrets API (create, get, versions,
> properties, soft delete, recover, purge) on {{/devstoreaccount1-keyvault}}.
> The Java SDK enforces HTTPS and challenge-based authentication, so the client
> needs a token credential, TLS (or a policy that rewrites the scheme) and
> {{disableChallengeResourceVerification()}}.
> h4. Change
> * Add a {{camel-test-infra-azure-key-vault}} module that starts Floci AZ and
> builds a {{SecretClient}} for it.
> * Run the producer operations (createSecret, getSecret, deleteSecret,
> purgeDeletedSecret and the others) against it through the {{secretClient}}
> option; keep the remote mode.
> * Skip the integration tests on ppc64le and s390x.
> h4. Not covered
> The {{azure:}} properties function always builds
> {{https://<vaultName>.vault.azure.net}}, so
> {{KeyVaultPropertiesSourceNoEnvTestIT}} stays remote only. Pointing the
> function at another endpoint would be a component change of its own.
> Depends on CAMEL-26615.
> _Claude Code on behalf of Andrea Cosentino_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
