This file is used to list changes made in each version of the runit cookbook.
- Make call to shell_out compatible with Ruby 3
- Add resource_name and allowed_actions to the resource for compatibility with more Chef Infra Client releases- @tas50
- Chef Infra Client 16 compatibility fixes - @xorimabot
- Chef Infra Client 16 compatibility
- Standardise files with files in chef-cookbooks/repo-management - @xorimabot
- Update Debian specs - @tas50
- Cookstyle fixes - @tas50
- Remove unnecessary Foodcritic comments - @tas50
- Add github actions testing - @tas50
- Remove Ubuntu 14.04 specs - @tas50
- Fix options property not taking on the legacy default value - @tas50
- Disable FC009 in the package resource - @tas50
- Fix comment typo - @tas50
- Wire up the service to actually use the status_command property - @tas50
- Add a new use_init_script_sv_link property - @tas50
- Test on Chef 14 and Chef 15 in Travis - @tas50
- Correct pass in the signal variable for the control config - @markan
- Remove Ubuntu 14.04 Kitchen tests - @tas50
- Add a new reload_log action - @tas50
- Resolve an undefined method error for sv_bin
- Fix the cookbook incorrectly requiring Chef 13 when it now actually requires Chef 14 due to the use of find_resource. Sorry about this everyone.
- This cookbook now requires Chef 13 or later. If you are still using Chef 12 please pin to the 4.3.1 release, and also seriously consider upgrading to the latest Chef to receive new features, bug fixes, and security updates in Chef.
- Performed a large-scale refactor of the resource to use the Chef resource DSL which resolves multiple edge case bugs by natively setting up properties, default values, and overrides
- Updated the default recipe to support Amazon Linux 2
- Default attributes used by the resource have been removed from the attributes file. They will continue to work, but their usage should be heavily discouraged as this mixed attributes + properties and results in confusion on where values come from.
- Formally deprecated the legacy
options
property in the readme - Removed some legacy backwards compatibility code for older Chef releases we no longer support
- Fixed broken integratino tests so we can better test this cookbook
- Added Amazon Linux 2 and Ubuntu 18.04 testing in Travis
- Consolidated mutliple helper methods into the resource itself for clarity
- Fixing plat_specific_sv_name logic to work with Amazon Linux 2 - @mbaitelman
- Fixing plat_specific_sv_name logic to work with Amazon Linux 2
- Fixing upstart logic to work with older Amazon versions
- Don't double start when creating new services
- Quoting the timeout value prevents it being cast to an unsigned long.
- Add a new log_flags property for changing the default -tt logging flag
- Make Ubuntu the same as Debian where we template out a script instead of symlinking /etc/init.d/servicename to sv
- Fix typo in an error message
- Also install the runit-systemd package on newer Ubuntus
- Remove chefspec matchers since they're auto generated by ChefDK now
- Amazon on Chef 12 fix and additional testing
- Add unit tests for each platform we support
- Remove the old attributes for controlling the service
- Remove the custom resource implementation that leaked in and was causing chefspec failures on Chef 12
- Convert all the service suite integration tests to inspec
- Don't fail on Debian 7 where the runsvdir init script doesn't exist
- Fix compile failures that caused chefspec and runtime failures
- Enable amazon linux testing of the default recipe in Travis
- Fail if we're on an unsupported platform in the main recipe instead of silently continuing
- Manage the actual runit service. Without this the runit service may not actually be started which means any service using runit won't actually start at boot
- Update the readme to not refer to providers and properly call the resource's property actual proeprties
- Add Debian testing to Travis
- Move file and templates out of the default dir since only Chef 11 needs this
- Use runit-systemd on Debian 9+ since runit package is actually designed for using runit as the main system init system
- Remove extra files from the test recipes
- Add a test for runit-systemd and use the process inspec resource
- Test with Local Delivery instead of Rake
- Update apache2 license string
- Fully support Amazon Linux
- Don’t mask errors from shellout helper if the binary is present.
- Don't error stopping a service that doesn't exist
- Cookstyle fixes
- Update the cookbook description
- Check that chef_version exists before declaring it
- Convert main suite test spec to inspec
- Add a number of debug statements to the provider to make debugging failed runs easier
- Fix faulty shell outs in the status commands that caused silent failures introduced in the 3.0.2 release
- Remove unused helper method runit_sv_works?
- Use our new official Oracle images in Test Kitchen
- Update wording to clarify that we’re deleting not ‘zapping’ files
- Don’t hang forever if Runit isn’t installed when using the provider
- Check for the runit binary before every shellout
- Remove Fedora support since it doesn’t work
- Set service to restart on env changes
- Testing updates
- Require Chef 12.1+
- Remove support for Gentoo as we have no way to test this
- Remove the empty library file
- Run specs against the latest RHEL 5
- Basic convergence testing in Travis CI
- Remove the need for apt in test kitchen
- Enable runit installation in Oracle Linux systems
- Remove double oracle in the metadata
- Breaking change: Removed support for EOL Ubuntu platforms (i.e. versions 6.10, 7.04, 7.10, 8.04) (#194)
- Added a dependency on yum-epel for RHEL platforms
- Breaking change: Removed logic which skipped waiting for named pipe when running inside Docker (#193)
- This cookbook is now managed by the Chef Community team and is located at http://www.github.com/chef-cookbooks/runit
- Cookbook development is now occurring on the master branch with releases taking place after merging. The development branch will be removed
- Added a .foodcritic file to ignore FC004
- Updated platforms to test in the Test Kitchen file
- Replaced the Cheffile with a Berksfile
- Moved the specs to the specs directory and removed logic to detect the depsolver
- Replaced Rubocop with Cookstyle
- Added basic testing in Travis CI
- Silenced deprecation warnings in the Chefspecs and removed the Chef 12.5 pin that was used to do the same previously
- Added maintainers.md and maintainers.toml files
- Removed Gentoo as an officially supported platform as we're not testing this
- Added additional RHEL derivatives as supported platforms in metadata.rb
- Added chef_version, source_url, and issues_url metadata to metadata.rb
- Add missing goals to Debian init script template (#175)
- Enhancement: Mark
env
files as sensitive (#182) - Reduce warning spam in Chef ~12.7 (#183)
- Enhancement: Add support for specifying supervising user and/or group for managing service (#187)
- Ensure
supervise/ok
named pipe is properly removed when disabling a service, so that it can be enabled again (#166, #167, #172) - Restore
restart_on_update
functionality originally added in #20 and lost in the 1.7.0 refactor. - Update test cookbooks to fix broken tests revealed by restoring
restart_on_update
functionality. Now using socat instead of netcat.
- Ensure the service directory exists so that we will succeed when enabling services (#153)
- Fix regression where env directory contents were being deleted when the
env
attribute is empty. (#144, #158) - Add
log_dir
attribute, used only whendefault_logger
is true. (#135) - Ensure svlogd configuration is linked into correct path (#83, #135)
- Update README and CHANGELOG for v1.7.0 to warn against known regressions (#144, #157)
- Avoid mutating resource options for Chef 12 compatability (#147, #150, #156)
- Fix regression regarding waiting for the service socket before running (#138, #142)
- Reimplement idempotence checks for
runit_service
resources (#137, #141) - Enhance ChefSpec unit test coverage with specs that step into the LWRP (#139)
- Deduplicate ServerSpec integration test coverage using example groups (#140)
- Re-add missing runit_service actions start, stop, reload and status
NOTE: With the benefit of hindsight we can say that the changes contained in this release merit a major version number change. Please be sure to test this new version for compatibility with your systems before upgrading to version 1.7.
- Modernize runit_service provider by rewriting pure Ruby as LWRP (#107)
- Modernize integration tests by rewriting Minitest suites as ServerSpec (#107)
- Fix regression in support for alternate sv binary on debian platforms (#92, #123)
- Fix regression in default logger's config location (#117)
- Tighten permissions on environment variable config files from 0644 to 0640 (#125)
- Add
start_down
anddelete_downfile
attributes to support configuring services with default state of 'down' (#105)
- Fedora 21 support
- Kitchen platform updates
- use imeyer's packagecloud repo for RHEL
- fix converge_by usage
- do_action helper to set updated_by_last_action
- style fixes to provider
- Add helper methods to detect installation presence
- Allow removal of env files(nhuff)
- Provide create action(clako)
- prevent infinite loop inside docker container
- runit service failing inside docker container
- move to librarian-chef for kitchen dependency resolution
- update tests
- updates to chefspec matchers
PR #53- Fix runit RPM file location for Chef provisionless Centos 5.9 Box Image
Fix runit RPM file location for Chef provisionless Centos 5.9 Box Image
Fixing string interpolation bug
Fixing assignment/compare error
- COOK-3950 - runit cookbook should use full service path when checking running status
- **[COOK-3267] - Improve testing suite in runit cookbook
- Updating test-kitchen harness
- Cleaning up style for rubocop
fixing metadata version error. locking to < 3.0
Locking yum dependency to '< 3'
[COOK-3560] Allow the user to configure runit's timeout (-w) and verbose (-v) settings
- COOK-3663 - Add ./check scripts support
- COOK-3271 - Fix an issue where runit fails to install rpm package on rehl systems
- COOK-3243 - Expose LSB init directory as a configurable
- COOK-3182 - Do not hardcode rpmbuild location
- COOK-3175 - Add svlogd config file support
- COOK-3115 - Add ability to install 'runit' package from Yum
- [COOK-2353]: Runit does not update run template if the service is already enabled
- [COOK-3013]: Runit install fails on rhel if converge is only partially successful
- [COOK-2549]: cannot enable_service (lwrp) on Gentoo
- [COOK-2567]: Runit doesn't start at boot in Gentoo
- [COOK-2629]: runit tests have ruby 1.9 method chaning syntax
- [COOK-2867]: On debian, runit recipe will follow symlinks from /etc/init.d, overwrite /usr/bin/sv
- [COOK-2477] - runit cookbook should enable EPEL repo for CentOS 5
- [COOK-2545] - Runit cookbook fails on Amazon Linux
- [COOK-2322] - runit init template is broken on debian
- [COOK-2353] - Runit does not update run template if the service is already enabled
- [COOK-2497] - add :nothing to allowed actions
- [COOK-2404] - allow sending sigquit
- [COOK-2431] - gentoo - it should create the runit-start template before calling it
- [COOK-2351] - add
run_template_name
to allow alternate run script template
- [COOK-2299] - runit_service resource does not properly start a non-running service
- [COOK-2254] - (formerly CHEF-154) Convert
runit_service
definition to a service resource namedrunit_service
.
This version has some backwards incompatible changes (hence the major version bump). It is recommended that users pin the cookbook to the previous version where it is a dependency until this version has been tested in a non-production environment (use version 0.16.2):
depends "runit", "<= 0.16.2"
If you use Chef environments, pin the version in the appropriate environment(s).
Changes of note
- The "runit" recipe must be included before the runit_service resource can be used.
- The
runit_service
definition created a separateservice
resource for notification purposes. This is still available, but the only actions that can be notified are:start
,:stop
, and:restart
. - The
:enable
action blocks waiting for supervise/ok after the service symlink is created. - User-controlled services should be created per the runit documentation; see README.md for an example.
- Some parameters in the definition have changed names in the resource. See below.
The following parameters in the definition are renamed in the resource to clarify their intent.
- directory -> sv_dir
- active_directory -> service_dir
- template_name -> use service_name (name attribute)
- nolog -> set "log" to false
- start_command -> unused (was previously in the "service" resource)
- stop_command -> unused (was previously in the "service" resource)
- restart_command -> unused (was previously in the "service" resource)
- [COOK-1576] - Do not symlink /etc/init.d/servicename to /usr/bin/sv on debian
- [COOK-1960] - default_logger still looks for sv-service-log-run template
- [COOK-2035] - runit README change
- [COOK-794] default logger and
no_log
forrunit_service
definition - [COOK-1165] - restart functionality does not work right on Gentoo due to the wrong directory in the attributes
- [COOK-1440] - Delegate service control to normal user
- [COOK-1008] - Added parameters for names of different templates in runit