[ 
https://issues.apache.org/jira/browse/GEODE-9156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17390125#comment-17390125
 ] 

ASF subversion and git services commented on GEODE-9156:
--------------------------------------------------------

Commit 22ac8760e9afad1cbec3e46e44afdba2f8c0d3c8 in geode's branch 
refs/heads/master from Owen Nichols
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=22ac876 ]

GEODE-9156: Replace docker-compose-rule with testcontainers (#6691)

* GEODE-9156: Replace docker-compose-rule with testcontainers in 
geode-connectors (#6378) (#6385)

Something to note when doing SSL testing: testcontainers does not let
you set the container name (using `container_name` in your compose.yml).
This ultimately means that reverse IP lookups produce hostnames that
look something like `project_service_index`. The problem is that these
names are not RFC compliant as they contain underscores. This can break
some aspects of SSL validation. I've had to work around this by renaming
containers in various test classes.

(cherry picked from commit a5335756a5801adf35ffdf4635b51cb17757eb84)
(cherry picked from commit 473af500ce43a4d35e08d4d750f3b5ed9186cc99)
(cherry picked from commit f537a5dded32d5386dccbb99a7e862b29811e269)

Co-authored-by: Jens Deppe <jde...@vmware.com>

> Switch from docker-compose to testcontainers
> --------------------------------------------
>
>                 Key: GEODE-9156
>                 URL: https://issues.apache.org/jira/browse/GEODE-9156
>             Project: Geode
>          Issue Type: Task
>          Components: membership
>            Reporter: Ernest Burghardt
>            Assignee: Jens Deppe
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.12.4, 1.13.4, 1.14.0, 1.15.0
>
>
> Palantir docker-compose-rule is sunsetting this month.  Palantir advises 
> switching to testcontainers' docker compose integration. We already use 
> testcontainer...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to