Puppet modules being skipped or failed to import should be reported or noticed by foreman.
The issue is if you have a syntax error within a puppet module, or even a general error that prevents foreman from using it. It should be shown as a notice ( not an error since this should be a graceful failure to import ).
I imported a module, with a silly mistake, which could have been avoided through the use of the puppet agent itself. However in lieu of modules I create it would be good to know if a module pulled from a third party source was faulty instead of indicating nothing has changed or happened.
#4 Updated by Dominic Cleal about 5 years ago
- Status changed from Duplicate to New
- Priority changed from Low to Normal
Correction: I'm reopening it as #3900 is a more complex requirement, since it may need some memorising of which class was imported from where, so when a syntax error occurs it can skip classes originally imported from the file with the error.
Note that the API will return a different response format and is only available on certain versions. It will return a 501 response if it isn't usable, so in that case, the original classes API should be used instead.