GitHub PushEvent at 2014-05-24 00:37:52
Repository: puppet
Actor: Iristyle
Payload: {"shas":[["f56da6cc626e568f4a8e25f65b384c775d635a20","46f1a0bd5592a2f9244ca321b129902a06b53e03@somethingsinistral.net","(maint) Simplify the CA use of the autosign setting\n\nCommit bca628dc adds proper conversion of autosign input values to\nbooleans, but Puppet::SSL::CertificateAuthority was still trying to\nhandle string values. This commit simplifies the checking logic and lets\nthe autosign setting handle data normalization.","Adrien Thebo",false],["265290bd8d8f10fe3452f4fd6638261ae1b2d6bb","e6fb06210fafc02fd7479ddbed2d042cc3a5155e@garretthoneycutt.com","(#PUP-1046) Add spec test for skeleton for generated modules\n\nThis patch adds a simple spec test to ensure that by including the\nclass with default values for all the parameters, that the class is\ncontained within the catalog.","Garrett Honeycutt",false],["c443433a01dd8979648e6f5dd2a780d7a4b84f9f","e6fb06210fafc02fd7479ddbed2d042cc3a5155e@garretthoneycutt.com","(#FORGE-38) Add Rakefile to skeleton for generated modules\n\nThis patch adds a simple Rakefile that provides rake tasks `lint` for\npuppet-lint, `validate` for validation of manifests, templates, and ruby\nfiles, and the tasks provided by the puppetlabs_spec_helper.","Garrett Honeycutt",false],["cc056e9a573bce9dfc9d32625383a9382732287b","e1ba3dbed1e582b1e25b820123fc2ddb5e0644ba@Alumni.TU-Berlin.de","(PUP-1586) allow managing existing cronjobs without caring for command\n\nWhen the catalog contains a cron resource that does not specify a value\nfor the command property, the transaction would fail with the cryptic\nerror message 'no command, somehow' under certain conditions.\n\nThis error is spurious. Generally, it's quite allowable to manage a subset\nof cron properties that does not include the command. Fixed by removing\nthe devfail invocation. The command property is now handled just like\nthe 'special' property.","Felix Frank",false],["5af17f01c4d6099a471dd7849a159e1ca244e3be","e1ba3dbed1e582b1e25b820123fc2ddb5e0644ba@Alumni.TU-Berlin.de","(PUP-1586) remove obsolete unit test\n\nThe cron type unit test titled \"it should require a command when adding\na new entry\" did not quite do what it said. What it actually tested was\nthat the type would raise an exception when an empty command should-value\nwas accessed.\n\nThis can be safely removed, as PUP-1587 will implement a more sensible\nprotection against the creation of cronjobs that lack a command, including\na working integration test.","Felix Frank",false],["d0fb26e7081aaef86bd0def9fe6e302970e5e33d","e1ba3dbed1e582b1e25b820123fc2ddb5e0644ba@Alumni.TU-Berlin.de","(PUP-1587) crontab: make sure that invalid crontabs aren't written out\n\nIt is permissible to manage cron entries and not manage the command\nproperty. However, if the entry doesn't exist on the target system yet,\npuppet should not try to create it.\n\nIn other words, a cron resource without a should value for the command\nproperty can only be synced to a valid state if the corresponding resource\non the target system has a valid command value already.\n\ncron { \"foo\": minute => 1 }\n\nis alright with an existing crontab of\n\n # Puppet Name: foo\n * * * * * /some/command\n\nbut not with a crontab not yet containing the entry named 'foo'.\n\nThis change prevents the sync operation in the error scenario.","Felix Frank",false],["b61fa207bc2084acdf4935d15d4c0e90d63074b4","e111443ffa1ca6dc6d0f49c67a475d335d39a3ce@redhat.com","(PUP-1879) Clear gem path cache when loading library features\n\nInstalling gems during a Puppet run should be picked up by features using the\n'libs' option.  However gems are installed into separate directories, so\nrubygems maintains an in-memory directory cache, which needs invalidating\nwhen attempting to load a library after installation.","Dominic Cleal",false],["a4abf13d353371c3568360f3101d01d4e3b7b4e6","cbab7d425a7df654ae235bdb1e5d3d10aa142973@gmail.com","(PUP-1769) yum provider takes install_options\n\nThe yum provider now supports install_options.","Jan Holčapek",false],["957016234b974ee18887500416c844f8945fd9ee","61215f28aa4ead37f3b7b292b12906cdf775d07c@gmail.com","(PUP-1769) Changing the has_feature to a one-liner","Peter Souter",false],["65055f3d037c20873d2b12c7f29f3beb75a73c2d","df6f0b2a1cc132c8326ed6a4a2fe90ec1147a191@puppetlabs.com","(maint) Use git mirrors for puppet/hiera/facter installation\n\nThe git server and fork used to construct git urls for installation\nprojects via beaker was previously hard set to be github.com and\npuppetlabs.  While we continue to default to these values, this commit\nallows them to be set globally or per installed project via environment\nvariables so that we can take advantage of internal and local git\nmirrors and daemons.","Josh Partlow",false],["2e5aa02160f6d74b34a131ba2904c716ca45c528","e3579b1e47f273529f0f929453e939a68ede9fd1@puppetlabs.com","(PUP-1552) Create new issue type for authorization\n\nAuthorization can be a tricky thing, but reporting it as a runtime error\nis misleading. This creates a new FAILED_AUTHORIZATION issue and labels\nthe failure to authorize because of the method as UNSUPPORTED_METHOD.","Andrew Parker",false],["d49b338a3337aef208e39bd976154f67b3b51c87","7cdd076e25adef0e25d3fedc5490d7fb59f5b1c0@puppetlabs.com","(pup-1952) Add jruby-19mode to travis ci (but under allow_failures)","Kylo Ginsberg",false],["fd46322d2978161a3af73ff8fc0a24e00898bbb5","7cdd076e25adef0e25d3fedc5490d7fb59f5b1c0@puppetlabs.com","(pup-1952) Break out jruby versions of gems as needed","Kylo Ginsberg",false],["8b86229e4649b1fe7adc96d93f5bec2ab8d675a8","7cdd076e25adef0e25d3fedc5490d7fb59f5b1c0@puppetlabs.com","(pup-1952) Accomodate that jruby can't fork","Kylo Ginsberg",false],["f10145b4d2457e0453abb2e3cbbb756a65829124","7cdd076e25adef0e25d3fedc5490d7fb59f5b1c0@puppetlabs.com","(pup-1952) Increase jruby heap size for travis CI","Kylo Ginsberg",false],["1ea83842d3cb8c801b07de1d0f6336df69067e2c","038619de7070e9c37fa7b69acb5e672d0c9a05bf@spotify.com","(PUP-1962) Fix class relationships\n\nFixes the following manifest: Class[foo] -> Class[bar]\n\nWould fail with undefined local variable or method `host_class'\nexception.","Erik Dalén",false],["5f0cb76fc3dd09aca5dd5d6441d99e64fd521bb8","970b4b19bdf132d0b4aef859a4378c1e31fe4af3@nordisch.org","(PUP-748) Fix the zypper package provider support for install_options.\n\nWhen install_options is a hash, the options are rendered with a space.\nThis is causing zypper to interpret the option incorrectly when\nusing Kernel.exec.\n\nFor example, this fails with \"unknown option '--from 1'\":\nKernel.exec 'zypper', 'install', '--from 1', 'vim'\n\nWhile this succeeds:\nKernel.exec 'zypper', 'install', '--from=1', 'vim'\n\nThe fix is to use the supported option syntax that uses\nan equal sign instead of a space.\n\nAlso flattening the options instead of joining them so that\nmultiple options in a hash are not interpreted as a single option.","Marcus Rückert",false],["607a1bca09da29a73c8929d1c635bb85452af166","aab4da3e71c2ca1ec0b8dbe613e4e9afa2218fcf@puppetlabs.com","(PUP-748) Add specs for zypper install_options.\n\nRemove expected nil when calling execute without install_options.\n\nAdd specs for install_options as a hash, array, or string.","Peter Huene",false],["ec709a16769b1b467772ea8f659a23a1106a43b6","95e828102f92afbaa4d3ed92646a950670566628@cloudsmith.com","Merge pull request #2439 from zaphod42/issue/master/pup-1552-not-authorize-reported-as-runtime-error\n\n(PUP-1552) Create new issue type for authorization","Henrik Lindberg",false],["ea1a04bef489bd193e3f3cfaeb5d0e6fdd142682","470bc578162732ac7f9d387d34c4af4ca6e1b6f7@bob.sh","PUP-1975 Add environment information to facts save during compilation\n\nPreviously the save method on the indirector was called without including\nthe environment information. This patch includes the environment so a custom\nterminus may utilize this information during storage.\n\nSigned-off-by: Ken Barber <ken@bob.sh>","Ken Barber",false]],"size":729,"ref":"refs/heads/master","head":"8cc786b44cded621903592cdea692a67c9510a9e"}