summaryrefslogtreecommitdiffstats
path: root/lib/puppet/rails/rails_resource.rb
diff options
context:
space:
mode:
authorMatt Robinson <matt@puppetlabs.com>2011-07-12 15:47:21 -0700
committerMatt Robinson <matt@puppetlabs.com>2011-07-12 16:06:22 -0700
commit45b3908e03734388b6c699ffbc4223f43b44a1d5 (patch)
treed082e9654a46f77e820fb17723a60ce252e201c2 /lib/puppet/rails/rails_resource.rb
parent1feccc3f2db29d112308a55032e7f93ca44b45aa (diff)
downloadpuppet-45b3908e03734388b6c699ffbc4223f43b44a1d5.tar.gz
puppet-45b3908e03734388b6c699ffbc4223f43b44a1d5.tar.xz
puppet-45b3908e03734388b6c699ffbc4223f43b44a1d5.zip
(#4142) Fix module check not to fail when empty metadata.json
Even though the puppet module tool was fixed to generate the required metadata attributes when it packages modules, it still creates an empty metadata.json file that gets checked into everybody's module repos. This causes the module to be unusable straight from a git clone since puppet was requiring all the required metadata attributes just with the presence of that file, and resulting in the error: No source module metadata provided for mcollective at This change makes it so that if you have an empty metadata.json (like the moduletool generates), puppet doesn't consider it to have metadata. If you have ANY metadata attributes in that file, it will still check to make sure all the required attributes are present. The work around up to this point has just been to delete the metadata.json file in git cloned modules. This also fixed the tests around this to actually run, since previously the tests depended on the a json feature, which we didn't have. We do, however, have a pson feature. Reviewed-by: Nick Lewis <nick@puppetlabs.com>
Diffstat (limited to 'lib/puppet/rails/rails_resource.rb')
0 files changed, 0 insertions, 0 deletions