Releases: danieldreier/autosign
Releases · danieldreier/autosign
v1.0.0
This is a major release with some changes that might affect some people.
Ruby 2.4 is now required.
Deep_merge 1.2.1 is now required.
While this release mostly consists of maintenance related items there are a few notable features.
New Features
- This new feature added is the ability to specify your validators and the order they are processed in.
- Greatly reduced logging. There were a lot of extra logging that was not necessary. This cleans up the code to only log when something actually changed.
- Previous all the validators ran every time. Now if a single validator passes, the other validator code is not run. This will save time and unnecessary code execution of multiplexers.
Full Changelog
- (maint) Update rake to 13.0
- (maint) print config in yaml format
- (maint) Fix a cache bug where the settings were loaded multiple times
- (maint) Fix a bug where the config overwrites settings
- (maint) Fix bug with validation order
- (maint) The autosign gem now requires the deep_merge gem 1.2.1
- (maint) The require_all has been dropped and is no longer a dependency
- (maint) Fix deprecation warnings with gemspec file
- (maint) Objectify the validator classes
- (maint) Fix a cache bug where the settings were loaded multiple times.
This was causing overzealous logging - (feat) Add an ordered validator list
- (feat) Any validator should short circuit
- (feat) Allow user to specify validation order
This release removes support for ruby < 2.4.
v0.1.4
Bug fixes:
- Use multi_json to allow a variety of JSON engines to be used, which makes installation easier.
- Read all of STDIN regardless of whether we’ll use it in order to avoid a bug in Java 8.
- Change yard from a runtime dependency to a dev dependency.
- Security updates for dependencies:
- Bump ffi from 1.9.10 to 1.9.25
- Bump yard from 0.9.12 to 0.9.20
v0.1.3
Bug fixes
- Fix config file path; the latest version of puppet-autosign creates config files in
/etc/puppetlabs/puppetserver/autosign.conf
but we weren't checking there - @reidmv fixed a bug where the decoder would error when presented with a csr with no challengePassword
- added an Apache license to be explicit about how the code is licensed. Did check with all contributors first.