Metadata Valid
No translation
With the recent addition of proxy support, I found it was missing proxy support for the mysql-connector. It also was missing puppet-archive support.
We run Jira in a cluster setup (pacemaker). For that we need to have the homedir of Jira (which is also the "data" directory) on a NFS share. The NFS mount is done to another directory and the data dir is a symlink, which is managed outside of this jira module. To be able to do that, i needed to fix the jira module to not handle the homedir, if done from outside. I think it will be useful for others, who are building similar setups, hence this pull request.
n/a
<!--
Thank you for contributing to this project!
-->
This adapts the templates for java-check, server.xml and setenv to the state of the 8.7.1 tarball, while keeping required modifications in place.
I thought about setting stuff depending on the installed java version, however not everyone installs java also via puppet and if ones does it, it must not necessarily be via the java puppet module.
Maybe we need an additional parameter to the module stating the java version?
Fixes #300
With java-11-openjdk-11.0.7.10 the option "PrintGCTimeStamps" can't be used as a parameter on the JVM. Therefore this PR adds the capability to remove the parameter from setenv.sh.
Fixes the issue, that PrintGCTimeStamps is hardcoded in setenv.sh.erb template which results in a JVM startup error when java-11-openjdk is used.
Templatizing the JVMEXTRAARGS parameter in setenv.sh to be able to accommodate custom settings.
<!--
Thank you for contributing to this project!
-->
This adapts the templates for java-check, server.xml and setenv to the state of the 8.7.1 tarball, while keeping required modifications in place.
I thought about setting stuff depending on the installed java version, however not everyone installs java also via puppet and if ones does it, it must not necessarily be via the java puppet module.
Maybe we need an additional parameter to the module stating the java version?
Fixes #300
<!--
Thank you for contributing to this project!
-->
<!--
Replace this comment with a description of your pull request.
-->
<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->
<!--
Thank you for contributing to this project!
-->
<!--
Updated the tomcat connectors based on Atlassians Jira Software Upgrade notes.
More information under: https://confluence.atlassian.com/jirasoftware/jira-software-7-13-x-upgrade-notes-957135908.html
-->
<!--
Use format:
Fixes #269
-->
@ffrank I wasn't aware of the voxpupuli/puppet-extlib#63 at the time I wrote this patch. But it seems to describe a similar issue.
I opened this pull request to start the discussion.
At the moment, I set redirect https only if:
you set the version variable to 7.1.0 and up
and
if you set both tomcatredirecthttpsport and tomcatnative_ssl
It's safe to say that 7.1.0 accept this config and I dont' want to mess the web.xml file if you don't want to redirect. But I would like to know how we determine we need to redirect. I'm pretty sure that you might want to redirect even without $tomcatredirecthttps_port?
Is only tomcatnativessl is enough?