[
https://issues.apache.org/jira/browse/CAMEL-20123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793001#comment-17793001
]
Ivan Kulaga edited comment on CAMEL-20123 at 12/4/23 6:34 PM:
--------------------------------------------------------------
ive made the pr, apparently someone should approve running check workflows on
it:
[https://github.com/apache/camel/pull/12309]
was (Author: JIRAUSER303138):
ive made a pr, apparently someone should approve running check workflows on it:
https://github.com/apache/camel/pull/12309
> camel-test-infra: externalize container information
> ---------------------------------------------------
>
> Key: CAMEL-20123
> URL: https://issues.apache.org/jira/browse/CAMEL-20123
> Project: Camel
> Issue Type: Task
> Components: camel-test-infra
> Affects Versions: 4.3.0
> Reporter: Otavio Rodolfo Piske
> Priority: Major
> Labels: help-wanted
> Fix For: 4.x
>
>
> Currently, our test-infra code refers to containers in code. For instance:
> {code:java}
> public static final String DEFAULT_ELASTIC_SEARCH_CONTAINER =
> "docker.elastic.co/elasticsearch/elasticsearch:8.11.1";
> ...
> ElasticsearchContainer elasticsearchContainer = new
> ElasticsearchContainer(DEFAULT_ELASTIC_SEARCH_CONTAINER)
> {code}
> 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.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
