[jira] [Commented] (UNOMI-479) Docker image will not start if elastic search needs authorization

["Serge Huber (Jira)" <ji...@apache.org>]

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

Serge Huber commented on UNOMI-479:
-----------------------------------

UNOMI-478 was closed because the properties already exist

org.apache.unomi.elasticsearch.username=${env:UNOMI_ELASTICSEARCH_USERNAME:-}
org.apache.unomi.elasticsearch.password=${env:UNOMI_ELASTICSEARCH_PASSWORD:-}

So we just need to modify entrypoint.sh to make use of them.


> Docker image will not start if elastic search needs authorization 
> ------------------------------------------------------------------
>
>                 Key: UNOMI-479
>                 URL: https://issues.apache.org/jira/browse/UNOMI-479
>             Project: Apache Unomi
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.0.0, 1.5.5
>            Reporter: Risto
>            Priority: Major
>
> This issue can not be saved properly before UNOMI-478 is solved.
>  
> Existing docker uses ./entrypoint.sh which will start unomi if elastic (ES) is available. It uses the env variable UNOMI_ELASTICSEARCH_ADDRESSES. That's why to connect to elastic with credentials you have to change it to UNOMI_ELASTICSEARCH_ADDRESSES=elastic:password@localhost:9200 inside docker-compose.yaml.
> But UNOMI_ELASTICSEARCH_ADDRESSES is used by unomi to connect to elastic search and must be equal to "hostname:port", otherwise unomi will not connect to ES.
>  
> So there is an environment variable conflict. The way to solve it consistent is to add new environment variables ELASTIC_USERNAME, ELASTIC_PASSWORD. Please see UNOMI-478 to understand why it is important.
>  
> Once new variables are added entrypoint.sh can must be modified to use it to properly connect to ES.



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