Issue #1387 has been reported by immerda. ---------------------------------------- Bug #1387: parseonly fails when using custom types http://reductivelabs.com/redmine/issues/show/1387
Author: immerda Status: Unreviewed Priority: Normal Assigned to: Category: Target version: Keywords: parseonly, custom types Complexity: Unknown Patch: None Affected version: 0.24.4 If I have cutom types, like the mysql type from DavidS and use them in manifests, the manifests will fail with the parseonly option. It seems obvious that puppet can't know anything from your own types and therefor the type is unknown to it. However if you'd like to use parseonly as a sytax checker, this behaviour is obviously not that cool. On the otherside for a complete syntax check parseonly should fail on unknown types. Maybe this problem could be "solved" by adding a --ignoreunknowntypes option to the --parseonly option, like the --ignoreimports option. A better, but I think more complicated, solution would be to have an additional option to pass additional (module) directories to the --parseonly option, where the custom types can be looked up. We'd like to use the parseonly option for syntax checking while checking in, however as we use custom types we can't currently use it. ---------------------------------------- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
