All notable changes to this project (since v4.0.0) will be documented in this file. The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
/etc/koji-hub/hub.confworld-readable with DB connection password
- Fedora 34 support (builders only)
- refreshed templates against
koji-1.21.1-1.el7andkoji-builder-1.22.1-1.fc33 - allow httpd to follow symlinks for static content and local product branding
puppetlabs-postgresqlmodule dependency now allows version 7
- Fedora 31 support
- Fedora 32-33 support
- work around for
python-simplejsonfor Koji < 1.11.0 (no longer needed) - Fedora 29-30 support
- CentOS 8 support missing
ssl.conftemplate
- Fedora 31 support
- Fedora 28 support
- CentOS 8 support
puppetlabs-concatmodule dependency now allows version 6puppetlabs-postgresqlmodule dependency now allows version 6puppetlabs-stdlibmodule dependency now allows version 6
- parameters:
koji::builder::max_jobskoji::builder::rpmbuild_timeoutkoji::builder::sleep_timekoji::gc::policiesfor Hiera driven declarations
- module dependencies:
doubledog-ddolibpuppetlabs-stdlib
- data types:
Koji::Gc::SeqKoji::GpgKeyIdKoji::Traceback
koji::gc::policy::seqnow also accepts integer values- freshen version requirement on
doubledog-cronmodule
koji::utils::ensureparameter:- enforces values suitable for files, but doesn't accept most for packages
- is not honored
koji::gc::unprotected_keysparameter:- did not accept key names as documented
- documentation did not mention allowance of key IDs
spin-livemediatasks fail on Fedora-based Koji Builderspycdioandpython2-kickstartpackages are still required there
- Koji Builders on Fedora 30 fail with
Generic Error: install librepo or yum
client_certparameter to thekoji::cli::profiledefined type.server_caparameter to thekoji::cli::profiledefined type.- Fedora 30 support
- Improved documentation for the
koji::cli::profiledefined type. - Absolute namespace references have been eliminated since modern Puppet versions no longer require this.
- Fedora 27 support
puppetlabs-concatdependency now allows version 5
- X.509 certificate management may cause
No such file or directoryerrors because the directory to which they are to be deployed has not yet been created by the appropriate package installation.
This and prior releases predate this project's keeping of a formal CHANGELOG. If you are truly curious, see the Git history.