Skip to content

chore(camel-test-infra-hashicorp-vault): upgrade hashicorp.vault.container to 2.0.0#22678

Open
github-actions[bot] wants to merge 1 commit intomainfrom
automated/upgrade-hashicorp-vault-container-2.0.0
Open

chore(camel-test-infra-hashicorp-vault): upgrade hashicorp.vault.container to 2.0.0#22678
github-actions[bot] wants to merge 1 commit intomainfrom
automated/upgrade-hashicorp-vault-container-2.0.0

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

This PR updates the hashicorp.vault.container container image to version 2.0.0.

Update Details

  • Property: hashicorp.vault.container
  • Image: mirror.gcr.io/hashicorp/vault
  • File: /home/runner/work/camel/camel/test-infra/camel-test-infra-hashicorp-vault/src/main/resources/org/apache/camel/test/infra/hashicorp/vault/services/container.properties
  • Old version: 1.21.4
  • New version: 2.0.0

Verification

Please verify:

  • Container image version is compatible with existing tests
  • No breaking changes in the updated version
  • Tests pass with the new version

Run the following to rebuild the test infra:

mvn clean verify -pl camel-test-infra-hashicorp-vault

Then test the impacted components.


This PR was automatically created by the Container Version Upgrade workflow.

…ainer to 2.0.0

Update hashicorp.vault.container from 1.21.4 to 2.0.0
@github-actions github-actions bot added dependencies Pull requests that update a dependency file container-images For check container upgrades automated For Check Container upgrade labels Apr 20, 2026
@apupier apupier self-assigned this Apr 20, 2026
Copy link
Copy Markdown
Contributor

@apupier apupier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it will be better to wait for this fix hashicorp/vault#31919 to avoid adding specific workaround that will become soon obsolete

with current state, we have:

Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out waiting for log output matching '.*Development.*mode.*should.*'

due to this kind of error:

unable to set CAP_SETFCAP effective capability: Operation not permitted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated For Check Container upgrade container-images For check container upgrades dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant