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

Attach files

Attach Screenshot

Voters

Watch issue

Watchers

Create sub-task

Link

Clone

Update Comment Author

Replace String in Comment

Update Comment Visibility

Delete Comments

XML

Word

Printable

JSON

Details

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

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.