parser=future ; puppet version 3.8; how to find/validate removed/deprecated features in current code all errors at once.

394 views
Skip to first unread message

rhpupp...@gmail.com

unread,
Sep 20, 2015, 11:08:58 PM9/20/15
to Puppet Users
We are using puppet 3.8. I'm currently testing our existing modules compatibility with puppet 4 using parser = future option in puppet.conf. When i run puppet agent against to this master server, it is showing one error at a time. once i fix the error, its showing another error. We have multiple resources wanted to work on updating the existing code to make it work for puppet 4. 

Is there a way we can validate all our existing module(s) for puppet 4 compatibility and get all errors at one time, so we can save lot of time in updating our existing modules.

Thomas Müller

unread,
Sep 21, 2015, 6:45:24 AM9/21/15
to Puppet Users


Am Montag, 21. September 2015 05:08:58 UTC+2 schrieb rhpupp...@gmail.com:
We are using puppet 3.8. I'm currently testing our existing modules compatibility with puppet 4 using parser = future option in puppet.conf. When i run puppet agent against to this master server, it is showing one error at a time. once i fix the error, its showing another error. We have multiple resources wanted to work on updating the existing code to make it work for puppet 4. 

Is there a way we can validate all our existing module(s) for puppet 4 compatibility and get all errors at one time, so we can save lot of time in updating our existing modules.

puppet-lint should detect many problems related to puppet 4 compatability.  


- Thomas

Henrik Lindberg

unread,
Sep 21, 2015, 9:04:10 AM9/21/15
to puppet...@googlegroups.com
On 2015-21-09 5:08, rhpupp...@gmail.com wrote:
> We are using puppet 3.8. I'm currently testing our existing modules
> compatibility with puppet 4 using parser = future option in puppet.conf.
> When i run puppet agent against to this master server, it is showing one
> error at a time. once i fix the error, its showing another error. We
> have multiple resources wanted to work on updating the existing code to
> make it work for puppet 4.
>
> *Is there a way we can validate all our existing module(s) for puppet 4
> compatibility and get all errors at one time, so we can save lot of time
> in updating our existing modules.*

If you are a PE user, you can get the Catalog Preview module from the
forge. It aggregates and reports all issues across all manifests in you
environment and then diffs the resulting catalog with one produced from
the same code without using the future parser. This tool is valuable to
iron out the subtle differences for which you do not get an error!

Requires a PE license.

Other alternatives are puppet-lint, or Geppetto IDE for puppet
development. Recommend using one of these first, then Catalog Preview.

Regards
- henrik

>
> --
> You received this message because you are subscribed to the Google
> Groups "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to puppet-users...@googlegroups.com
> <mailto:puppet-users...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/5680f16c-7da6-49cb-957d-fe323dfd24b4%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/5680f16c-7da6-49cb-957d-fe323dfd24b4%40googlegroups..com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.


--

Visit my Blog "Puppet on the Edge"
http://puppet-on-the-edge.blogspot.se/

Reply all
Reply to author
Forward
0 new messages