Version 5.0.0 is a major release of the puppet/jira module. The API stays mostly the same, but there are a few changes that users should take into account:
Only JIRA version 8.0.0 and newer are supported.
The module's templates have been synchronized with the latest LTS release of JIRA (8.13.5)
Upgrade your JIRA installation to a supported version using a previous version of this module first.
The jira::facts class has been removed
The jira_version fact is no longer required for upgrades and the facts weren't particularly useful, so they have been removed. The module will not remove existing files, however, so existing installations will continue reporting jira facts.
Note: upgrading to this version will cause jira to restart once due to the way updates are detected. If you would like to avoid this, create a ${jira::installdir}/atlassian-${jira::product_name}-running symlink pointing to your current active installation.
Default versions have changed
The module will now install 8.13.5 by default. If you for some reason don't explicitly specify a JIRA version in your installation, you will get an automatic upgrade.
The MySQL connector, if installed, is now 8.0.23 by default, as the previous default is EOL.
The API is now typed
The type enforcement is mostly backwards compatible, but some variables which previously accepted integer-looking strings will now require actual integers.
Database configuration is overhauled
Most settings in dbconfig.xml are now omitted of not explicitly configured by the user. JIRA will fall back to its built-in default values, which mostly matched what the module configured previously.
If this causes adverse effects with your installation, please report a bug.
jira::poolsize is now a deprecated parameter and merely an alias for $jira::pool_max_size. If both are configured, the latter takes precedence. Jira's default value for this parameter is 20, which matches the module's previous default
jira::enable_connection_pooling is now deprecated and has no effect. It previously only affected users using PostgreSQL databases, and served no useful purpose.
Changes to default behaviour
We now use the camptocamp/systemd module, and the unit file is installed in /etc/systemd/system/jira.service. The old file at /lib/systemd/system/jira.service can be removed, though its existence should not matter.
jira::java_opts no longer defaults to -XX:-HeapDumpOnOutOfMemoryError as it is not on by default in Atlassian's configuration. If you want this, please add it to your configuration explicitly. The old name for the parameter is maintained
The module selects some defaults for setenv.sh based on the value of jira::jvm_type. This parameter defaults toopenjdk-11. You may override the module's choices by using the new jira::jvm_gc_args, jira::jvm_code_cache_args and jira::jvm_extra_args parameters. For backwards compatibility, JVM_SUPPORT_RECOMMENDED_ARGS is configured by jira::java_opts
Broken / deprecated functionality has been removed
The jira::service class is now private, and overriding the service template is no longer possible. Use systemd drop-ins instead.
Only puppet/archive is supported for downloading the installation packages, and this is not configurable
jira::format no longer exists; it's always tar.gz. This parameter never worked properly.
Version 5.0.0 is a major release of the
puppet/jiramodule. The API stays mostly the same, but there are a few changes that users should take into account:Only JIRA version 8.0.0 and newer are supported.
The
jira::factsclass has been removedjira_versionfact is no longer required for upgrades and the facts weren't particularly useful, so they have been removed. The module will not remove existing files, however, so existing installations will continue reporting jira facts.${jira::installdir}/atlassian-${jira::product_name}-runningsymlink pointing to your current active installation.Default versions have changed
The API is now typed
The type enforcement is mostly backwards compatible, but some variables which previously accepted integer-looking strings will now require actual integers.
Database configuration is overhauled
dbconfig.xmlare now omitted of not explicitly configured by the user. JIRA will fall back to its built-in default values, which mostly matched what the module configured previously. If this causes adverse effects with your installation, please report a bug.jira::poolsizeis now a deprecated parameter and merely an alias for$jira::pool_max_size. If both are configured, the latter takes precedence. Jira's default value for this parameter is 20, which matches the module's previous defaultjira::enable_connection_poolingis now deprecated and has no effect. It previously only affected users using PostgreSQL databases, and served no useful purpose.Changes to default behaviour
camptocamp/systemdmodule, and the unit file is installed in/etc/systemd/system/jira.service. The old file at/lib/systemd/system/jira.servicecan be removed, though its existence should not matter.jira::java_optsno longer defaults to-XX:-HeapDumpOnOutOfMemoryErroras it is not on by default in Atlassian's configuration. If you want this, please add it to your configuration explicitly. The old name for the parameter is maintainedsetenv.shbased on the value ofjira::jvm_type. This parameter defaults toopenjdk-11. You may override the module's choices by using the newjira::jvm_gc_args,jira::jvm_code_cache_argsandjira::jvm_extra_argsparameters. For backwards compatibility,JVM_SUPPORT_RECOMMENDED_ARGSis configured byjira::java_optsBroken / deprecated functionality has been removed
jira::serviceclass is now private, and overriding the service template is no longer possible. Use systemd drop-ins instead.puppet/archiveis supported for downloading the installation packages, and this is not configurablejira::formatno longer exists; it's alwaystar.gz. This parameter never worked properly.