The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

This issue tracker is now in read-only archive mode and automatic ticket export has been disabled. Redmine users will need to create a new JIRA account to file tickets using https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:

Bug #21969

metadata.json without source throws unclear errors

Added by Hubert de Heer almost 3 years ago. Updated almost 3 years ago.

Status:DuplicateStart date:
Priority:NormalDue date:
Assignee:Charlie Sharpsteen% Done:

0%

Category:modules
Target version:-
Affected Puppet version:3.1.1 Branch:
Keywords:metadata.json

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com


Description

Using a Geppetto version that contained a bug (https://github.com/cloudsmith/geppetto/issues/536), the generated metadata.json didn’t contain a “source” entry. Apparantly this field is a require field in metadata.json. Puppet (3.1) will throw weird errors (Class not found / Could not find template) when source field is not present in metadata.json. If puppet always loads the metadata.json when present it might be handier to throw an error that makes more sense when a metadata.json is not in the expected format.

We test our modules on a local Vagrant/Virtualbox setup so the metadata.json is always picked up.


Related issues

Duplicates Puppet - Bug #20728: Invalid metadata.json in module root causes Error 400 Investigating

History

#1 Updated by Charlie Sharpsteen almost 3 years ago

  • Category set to modules
  • Status changed from Unreviewed to Duplicate
  • Assignee set to Charlie Sharpsteen

Looks like this is a duplicate of #20728. I’ll dig in and see what I can find.

Also available in: Atom PDF