{"shas":[["885c9cdc91760f858601b85a7bdbb4d9f20810d9","33f5d68b41be5af447cafdf50d91452cb416a335@puppetlabs.com","Merge branch 'ticket/2.7.x/7114fixup' of https://github.com/stschulte/puppet into 2.7rc","Matthaus Litteken"],["bc4051658bf6e057819f23eea7a138d34efd1f9d","75ef9faee755c70589550b513ad881e5a603182c@puppetlabs.com","Fix order dependent spec failure in exec specs\n\nThe provider/exec/windows_spec.rb spec was creating exec resources\nexplicitly using the Windows provider as the provider. The Windows\nprovider was being evaluated as suitable and thus the default provider\nfor the type. Then in future specs, it could be used since it was the\ndefault, even though it wasn't necessarily suitable, causing failures.\nNow, we just clear the defaultprovider on the exec type after all the\nspecs in the file have finished, ensuring it will be recalculated\nappropriately when needed.\n\nReviewed-By: Matt Robinson <matt@puppetlabs.com>","Nick Lewis"],["7a39ca72e64d9ca07875fd41d60f23140d6195d9","1fa2ef4755a9226cb9a0a4840bd89b158ac71391@puppetlabs.com","(#8667) Write out a list of resources that are managed by puppet agent\n\nSimilar to how the Puppet classes are written out each catalog apply,\nthe list of resources is now being written out to a text file that can\nbe easily used by tools like MCollective.  This allows tools that do\nad-hoc management of resources to know if they're changing a resource\nthat puppet manages, and adjust behavior accordingly.\n\nReviewed-by: Nick Lewis <nick@puppetlabs.com>","Matt Robinson"],["5df6924d047e8b87173a6e12107a8fdc3defb3b2","1fa2ef4755a9226cb9a0a4840bd89b158ac71391@puppetlabs.com","Merge branch 'ticket/2.7rc/8667-write_managed_resources' into 2.7rc\n\n* ticket/2.7rc/8667-write_managed_resources:\n  (#8667) Write out a list of resources that are managed by puppet agent","Matt Robinson"],["da69637e32a267c0133b0eeb902065ed56d8935d","75ef9faee755c70589550b513ad881e5a603182c@puppetlabs.com","Fix failing spec for resource file\n\nThis spec was trying to cause a failure to write the resource file by\nusing the incorrect location \"//bad file\". However, this location is\nactually perfectly valid, so the write was succeeding, and the spec was\nfailing. Now we use a genuinely unwritable location.","Nick Lewis"],["79fb5b3780fdf4acda42aea4b85b25a69525422b","33f5d68b41be5af447cafdf50d91452cb416a335@puppetlabs.com","Merge pull request #119 from nicklewis/ticket/2.7rc/8667-spec-fix\n\nFix failing spec for resource file","Matthaus Litteken"],["fe92f20a5e904a2350b41d7c67dc61d0194060b8","33f5d68b41be5af447cafdf50d91452cb416a335@puppetlabs.com","(#9440) Allow cron vars to have leading whitespace\n\nPatch applied from Jeremy Thornhill. This allows whitespace to appear before\ncron variables. Previously, whitespace before cron variables would trigger a\nparse failure, and the crontab, except for the puppet managed portion, would\nget removed. This addresses that issue. It also includes a test for this issue,\nadded into the tests directory, which seems to be where the crontab tests live.\n\nSigned-off-by: Matthaus Litteken <matthaus@puppetlabs.com>","Matthaus Litteken"],["515cc6c3e0068ac584f4469d97c79d82d8a589f6","75ef9faee755c70589550b513ad881e5a603182c@puppetlabs.com","Merge pull request #122 from haus/ticket/9440\n\nTicket/9440","Nick Lewis"],["9dd18cfcbf74995bde7bf18f6e3ddd47659d3daf","33f5d68b41be5af447cafdf50d91452cb416a335@puppetlabs.com","Updated CHANGELOG for 2.7.4rc3","Matthaus Litteken"],["368d4efa79d36ef3840694cc92e52920924810a9","33f5d68b41be5af447cafdf50d91452cb416a335@puppetlabs.com","Merge branch '2.7rc'","Matthaus Litteken"]],"ref":"refs/heads/master","size":10,"head":"368d4efa79d36ef3840694cc92e52920924810a9","push_id":43009302}