summaryrefslogtreecommitdiff
path: root/sysutils/ruby-chef-zero
AgeCommit message (Collapse)AuthorFilesLines
2017-06-30Add newline at EOF to ensure the +INSTALL script is generated correctly.jperkin1-1/+1
2017-06-18Enable ruby24.taca1-2/+2
2017-06-12Update ruby-chef-zero to 13.0.0.taca4-17/+47
* pkgsrc change: support ruby23 only. Changes from 3.2.1 is too many to write here, please refer <https://github.com/chef/chef-zero/blob/master/CHANGELOG.md>.
2017-06-06Set RUBY_VERSIONS_ACCEPTED correctly to fix scan failures.jperkin1-1/+3
2015-11-04Add SHA512 digests for distfiles for sysutils categoryagc1-1/+2
Problems found with existing digests: Package memconf distfile memconf-2.16/memconf.gz b6f4b736cac388dddc5070670351cf7262aba048 [recorded] 95748686a5ad8144232f4d4abc9bf052721a196f [calculated] Problems found locating distfiles: Package dc-tools: missing distfile dc-tools/abs0-dc-burn-netbsd-1.5-0-gae55ec9 Package ipw-firmware: missing distfile ipw2100-fw-1.2.tgz Package iwi-firmware: missing distfile ipw2200-fw-2.3.tgz Package nvnet: missing distfile nvnet-netbsd-src-20050620.tgz Package syslog-ng: missing distfile syslog-ng-3.7.2.tar.gz Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
2015-02-04Switch to depend ruby-hashi2 package.taca1-2/+3
Bump PKGREVISION.
2015-01-22Fix dependency.joerg1-2/+2
2015-01-19Update ruby-chef-zero to 3.2.fhajny3-10/+44
3.2 (9/26/2014) - removed 'json' gem dependency, replaced it with 'ffi-yajl' 3.1.3 (9/3/2014) - fixes for running Chef local mode in multi-org mode 3.1.2 (8/29/2014) - add default to rspec for cookbooks - add /organizations/NAME/organization/_acl as an alias for /organizations/NAME/organizations/_acl 3.1.1 (8/28/2014) - fix minor bug with unknown container acls 3.1 (8/28/2014) - New rspec data directives: organization, acl, group, container - Fix organizations POST to honor full_name - Fixes for enterprise rspec data loading - Fix invites not removing the invite when user is forcibly added to an org 3.0 (7/22/2014) - Enterprise Chef support (organizations, ACLs, groups, much more) - SSL support (@sawanoboly) 2.2 (6/18/2014) - allow port ranges to be passed in as enumerables, which will be tried in sequence until one works: ChefZero::Server.new(:port => 80.upto(100)) 2.1.5 (6/2/2014) - fix issue with :single_org => not being honored 2.1.4 (5/27/2014) - fix issue with global Thread.exit_on_exception being set 2.1.3 (5/27/2014) - rspec: default port to 8900 to not conflict with normal default port - rspec: when chef_zero_opts is set, check if current server has those options before continuing 2.1.2 (5/27/2014) - fix build_uri (and thus cookbook downloads) 2.1.1 (5/26/2014) - flip defaults off in V1ToV2Adapater, allowing most chef tests to pass against 2.1.1 2.1 (5/26/2014) - Multi-tenancy! If you set :single_org => nil when starting the server, you will gain /organizations/* at the beginning of all URLs. Internally, all endpoints are rooted at /organizations/ORG anyway, there is just a translation that goes on to add /organizations/single_org to the URL when someone hits chef-zero. - Fixes to support chef-zero local mode passing pedant
2014-06-03Import sysutils/ruby-chef-zero into pkgsrc.jperkin4-0/+97
Chef Zero is a simple, easy-install, in-memory Chef server that can be useful for Chef Client testing and chef-solo-like tasks that require a full Chef Server. It IS intended to be simple, Chef 11 compliant, easy to run and fast to start. It is NOT intended to be secure, scalable, performant or persistent. It does NO input validation, authentication or authorization (it will not throw a 400, 401 or 403). It does not save data, and will start up empty each time you start it. Because Chef Zero runs in memory, it's super fast and lightweight. This makes it perfect for testing against a "real" Chef Server without mocking the entire Internet.