This file is used to list changes made in each version of the djbdns cookbook.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
Fix markdown
Standardise files with files in sous-chefs/repo-management
- Remove delivery folder
- resolved cookstyle error: tasks/maintainers.rb:37:7 convention:
Style/FileWrite
- Standardise files with files in sous-chefs/repo-management
- Standardise files with files in sous-chefs/repo-management
- Sous Chefs Adoption
- Update Changelog to Sous Chefs
- Update to use Sous Chefs GH workflow
- Update test-kitchen to Sous Chefs
- Update README to sous-chefs
- Update metadata.rb to Sous Chefs
- Yamllint fixes
- MDL fixes
- Fix integration tests
- Add Ubuntu 20.04 testing
- Add a basic converge unit test - @tas50
- Make sure we have wget for source installs - @tas50
- Update Test Kitchen platforms - @tas50
- Add code owners file - @tas50
- Rename the kitchen config - @tas50
- Remove Ubuntu 14.04 testing for 18.04 - @tas50
- Delete the dangling dependency on ucspi-tcp - @RoboticCheese
- Stop creating the runit service directory - @RoboticCheese
- Resolve FoodCritic offenses - @RoboticCheese
- Test with Local Delivery and not Rake
- Move templates out of the default directory since only Chef < 12 requires this
- Require 12.5 and remove compat_resource dependency
- Require the latest compat_resource
- Switch to Inspec for integration testing
- Remove RHEL 5 testing as it's near EOL
- Prevent compile error with source updating method
- Add ChefSpec matchers
- Convert LWRP to a custom resource and use compat_resource for 12.1+ compatibility
- Make sure IPSEND is set so the cache starts
- Fix Chef 13 compatibility by updating manage_home
- Testing updates and remove FQDN from templates
- Update maintainers wording and format [skip-ci]
- Testing updates
- Require Chef 12.1+
This version removes support for bluepill and daemontools init systems and Arch Linux. If you rely on that support you'll want to pin to the 1.2.0 release
This version now manages all djbdns env files to be compatible with the newest runit release. If you manage these files outside of the djbdns recipe you'll need to use the new attributes
- Removed newlines in configs to prevent restarts
- Removed inclusion of ucspi-tcp recipe for source installs
- Convert hashes to Ruby 1.9+ format
- Bump Runit dependency to 1.6.0 from 1.5.0
- Updated Test Kitchen config with the latest platforms and a suite for source install
- Added Travis CI config
- Added a simple contributing doc to replace the Chef Software Inc version
- Updated the development gem requirements and break gems into groups in the gemfile
- Added a cookbook version badge in the readme
- Added a chefignore file to limit what files are uploaded to the chef server
- Added additional platforms to the metadata
- Add source_url and issues_url to the metadata
- Make modes strings to preserve the leading 0s
- Resolve rubocop warnings
- Added additional unit tests
- Update dependency for current runit cookbook, #7
- Debian is a source based platform, #9 (see issue for background)
- Add
package_name
attribute to allow for installing dbndns, #16, related to #9 - Use runit as default service type instead of bluepill, #10
- Drop explicit support for old unsupported Ubuntu versions, #11
- Manage runit's sv dir for "reasons," #12
- Remove attributes from metadata, as they're not used for anything anywhere anyway
- [COOK-2262] - pin runit dependency
- [COOK-1739] - use node attributes with hash notation instead of just the attribute name (ipaddress, domain) in djbdns attributes file
- [COOK-1742] - fix foodcritic warnings, use platform_family where apropriate
- [COOK-1259] - Support local (10.x, 172.x, 192.168.x) reverse lookups in cache
- [COOK-1042] - Corrected a syntax error in axfr.
- [COOK-740] - use correct directory for tinydns root data
The various recipes now support multiple service types. This is controlled with the node[:djbdns][:service_type]
attribute, which is set by platform in the default recipe.
ArchLinux support has been added, as well as naively attempting other platforms by source-compiled installation with bluepill for service management.