[CAMEL-20123] camel-test-infra: externalize container information

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.3.0
• Fix Version/s: 4.3.0
• Component/s: camel-test-infra
• Labels: help-wanted
• Estimated Complexity: Novice
• Assignee: Unassigned
• Reporter: Otavio Rodolfo Piske
• Created: 17/Nov/23 17:17
• Updated: 07/Feb/24 17:04
• Resolved: 07/Feb/24 17:04

Description

Currently, our test-infra code refers to containers in code. For instance:

public static final String DEFAULT_ELASTIC_SEARCH_CONTAINER = "docker.elastic.co/elasticsearch/elasticsearch:8.11.1";

...
ElasticsearchContainer elasticsearchContainer = new ElasticsearchContainer(DEFAULT_ELASTIC_SEARCH_CONTAINER)

The challenge with this approach is that we have to verify file by file if there is an upgrade to the containers.

Ideally, we should keep this information in a properties file named `containers.properties`. This could allow us to automate checking if there is an updated version of those containers and reduce the maintenance effort.

Issue Links

• links to: GitHub Pull Request #12309