[
https://issues.jboss.org/browse/WFWIP-178?page=com.atlassian.jira.plugin....
]
Michal Jurc commented on WFWIP-178:
-----------------------------------
[~jdenise]: Okay, I've gave this a bit of thought and from the point of view of
usability and supportability, I've came up with the following stories:
* As a user, I want to keep using my deployment with old parameters effortlessly (that
means if I replace template with new one, the build should act the same way).
* As a user, I want to be able to trim down my image with the same template not to have
1.07 GB builder image in deployment.
While it may be attractive (easy) to add templates to add the ability of performing
chained build, I personally think that updating all existing templates with a switch that
would allow the user to use the new abilities would be easier to use. I mean, all the
existing templates provide sensible use cases.
[Galleon] Script fails when JGROUPS_CLUSTER_PASSWORD is set by
template
-----------------------------------------------------------------------
Key: WFWIP-178
URL:
https://issues.jboss.org/browse/WFWIP-178
Project: WildFly WIP
Issue Type: Bug
Components: OpenShift
Reporter: Nikoleta Ziakova
Assignee: Jean Francois Denise
Priority: Blocker
Steps to reproduce:
# Provision server without jgroups subsystem, e.g.
https://github.com/nziakova/jboss-eap-quickstarts/tree/with_galleon_dir/k...
# Use
[
template|https://github.com/jboss-container-images/jboss-eap-7-openshift-...]
to deploy the application
The template sets default {{JGROUPS_CLUSTER_PASSWORD}} which causes the scripts fail:
{code}
ERROR "Cannot configure the jgroups authentication. The jgroups subsystem is not
present in the server configuration file."
{code}
It must be decided whether it is a bug in scripts or templates. Updating the templates
would cause backwards compatibility issues.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)