This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 0f5a123a3ef7 Camel-Cyberark-Vault: Improved docs
0f5a123a3ef7 is described below
commit 0f5a123a3ef7aa251fe00b2a17e0fb6dbf12fcfe
Author: Andrea Cosentino <[email protected]>
AuthorDate: Wed Nov 5 18:56:29 2025 +0100
Camel-Cyberark-Vault: Improved docs
Signed-off-by: Andrea Cosentino <[email protected]>
---
.../src/main/docs/cyberark-vault-component.adoc | 94 ----------------------
1 file changed, 94 deletions(-)
diff --git
a/components/camel-cyberark-vault/src/main/docs/cyberark-vault-component.adoc
b/components/camel-cyberark-vault/src/main/docs/cyberark-vault-component.adoc
index 09452ec8a1b5..63a37e18d8dd 100644
---
a/components/camel-cyberark-vault/src/main/docs/cyberark-vault-component.adoc
+++
b/components/camel-cyberark-vault/src/main/docs/cyberark-vault-component.adoc
@@ -323,97 +323,3 @@ mvn clean verify -Dit.test=CyberArkVaultProducerIT \
-Dcamel.cyberark.apiKey=YOUR_API_KEY_HERE
----
-==== Skipping Integration Tests (Default)
-
-By default, integration tests are skipped when system properties are not
provided:
-
-[source,bash]
-----
-# This will skip all integration tests
-mvn clean install
-----
-
-==== Test Scenarios Covered
-
-The integration tests cover:
-
-1. **Property Function Tests** (`CyberArkVaultPropertiesSourceIT`)
- - Simple secret retrieval using `{{cyberark:secret}}`
- - JSON field extraction using `{{cyberark:secret#field}}`
- - Default values using `{{cyberark:secret:defaultValue}}`
- - Complex secret paths with slashes
-
-2. **Component Endpoint Tests** (`CyberArkVaultProducerIT`)
- - Secret retrieval via component endpoint
- - Dynamic secret ID via message headers
- - Header verification (SECRET_ID, SECRET_VALUE)
-
-3. **Multiple Secrets Tests** (`CyberArkVaultMultipleSecretsIT`)
- - Multiple secrets in a single route
- - Multiple database configurations
- - Connection string construction
-
-==== CI/CD Integration Example
-
-For GitHub Actions:
-
-[source,yaml]
-----
-name: Integration Tests
-on: [push, pull_request]
-
-jobs:
- test:
- runs-on: ubuntu-latest
-
- services:
- postgres:
- image: postgres:15
- env:
- POSTGRES_PASSWORD: SuperSecretPg
- ports:
- - 5432:5432
-
- conjur:
- image: cyberark/conjur
- env:
- DATABASE_URL: postgres://postgres:SuperSecretPg@postgres/postgres
- CONJUR_DATA_KEY: W0BuL24xJMVfGNTKRxcC4xv76cKE7wNJh0AKXdvmnxk=
- ports:
- - 8080:80
-
- steps:
- - uses: actions/checkout@v2
-
- - name: Set up JDK 11
- uses: actions/setup-java@v2
- with:
- java-version: '11'
-
- - name: Initialize Conjur and Load Policies
- run: |
- # Wait for Conjur to start
- sleep 15
-
- # Create account and extract API key
- API_KEY=$(docker exec conjur conjurctl account create
myConjurAccount | grep "API key" | awk '{print $NF}')
- echo "CONJUR_API_KEY=$API_KEY" >> $GITHUB_ENV
-
- # Load test policies here...
-
- - name: Run Integration Tests
- run: |
- mvn clean verify \
- -Dcamel.cyberark.url=http://localhost:8080 \
- -Dcamel.cyberark.account=myConjurAccount \
- -Dcamel.cyberark.username=admin \
- -Dcamel.cyberark.apiKey=${{ env.CONJUR_API_KEY }}
-----
-
-=== Best Practices
-
-1. **Use API Keys**: For programmatic access, use API keys instead of passwords
-2. **Enable SSL Verification**: Always verify SSL certificates in production
-3. **Least Privilege**: Grant only necessary permissions to the Conjur identity
-4. **Secret Rotation**: Regularly rotate secrets and API keys
-5. **Environment Variables**: Use environment variables or secure
configuration for credentials
