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

ASF subversion and git services commented on ARTEMIS-2776:
----------------------------------------------------------

Commit 44e15b0e1ff5a24e39b7e94074525309c17a189d in activemq-artemis's branch 
refs/heads/master from zekeoptimo
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=44e15b0 ]

ARTEMIS-2776 Improve Dockerfiles

Fixes the Dockerfiles handling of ANONYMOUS_LOGIN and adds an
EXTRA_ARGS environment variable to allow specifying extra arguments
separate from the username, password and anonymous login options.


> Dockerfile Improvements
> -----------------------
>
>                 Key: ARTEMIS-2776
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2776
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>         Environment: Windows 10 running scripts in WSL
>            Reporter: Zeke Rogers
>            Priority: Minor
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The current Dockerfiles for Ubuntu and CentOS contain an environment variable 
> ANONYMOUS_LOGIN that is not actually being used, resulting in anonymous 
> logins always being allowed.
> In addition, the options "--http-host 0.0.0.0 --relax-jolokia" are included 
> by default, and overriding them would also require putting the username and 
> password in the  entire CREATE_ARGUMENTS environment variable, making the 
> previous ARTEMIS_USER and ARTEMIS_PASSWORD variables moot.
> This could be made easier to add extra options without having to re-specify 
> the username and the password. This is especially true in environments where 
> a secrets file may be used for usernames/passwords (such as Kubernetes) but 
> the rest of the args can be in plain text. In this scenario, having the 
> username and password as separate envrionment variables from the other 
> arguments is very beneficial.



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

Reply via email to