----- Original Message ----- > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Ah, > > So, if you have an existing code base that you've inherited and > you're going to be trying the 2.8 series of Puppet, where variable > scoping is > mandatory, how would you go about finding all out of scope variables > without actually writing code to call every portion of the puppet > code. > > I've used puppetdoc to find issues in the past but it doesn't seem to > care about variable scope from what I can tell. > > I'll try puppet-lint and see if it picks up on the issues but I'm > suspecting that it won't since it's probably not compiling the code.
The only sane way imho is to diff the catalogs. The catalogs are based on the variables, vars are interpolated into strings in the catalog and anything like versions, names etc that came from variables would be in the catalog already parsed. So if you diff'd a 2.6 and 2.8 catalog you would know if variable changes affected you. I did some extremely hacky thing to diff catalogs in the past[1] but I have no idea if this still works with 2.7 or 2.8 but I think this is the only real way to tell if you will have changes due to master changes. Would be nice if there was a migration tool written by someone who actually know the catalog internals :) Of course this does not tell you if the agent will interpret the catalog correctly... [1] https://github.com/ripienaar/puppet-catalog-diff > > Trevor > > On 01/05/2012 08:27 AM, Felix Frank wrote: > > On 01/03/2012 06:15 PM, Trevor Vaughan wrote: > >> Any takers? > > > > Please elaborate on the question. > > > > - -- > Trevor Vaughan > Vice President, Onyx Point, Inc. > email: tvaug...@onyxpoint.com > phone: 410-541-ONYX (6699) > pgp: 0x6C701E94 > > - -- This account not approved for unencrypted sensitive information > -- > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEcBAEBAgAGBQJPBvewAAoJECNCGV1OLcypG84H/1U/Ythc0aK9Ie6RTCT1LYkL > ZUAQP+3NVobFovevE99P1J90suyZPn5dp9KPF/eW4GPiwoJ+oz0Zx5CdbH9untIX > EZ+XlMIxS0y8mAUmwQzBoLu8ca7BjUTJeQBZBweiwxDwvzhnlzTsYPiGSs7iL85w > PQS26DFP+LHJCRZh/kKi2LC3mG/WfGvI5CeK1CXJp9Ieetq2lMafFLztZRoOq1/W > 5pHRHmCdvj7TiwGtvjdPbUsuimhF+FHgZu+X+QXf6kxSdIcwnEMVUJmHv/v4BfT5 > mkAT4r6PHhK/WcRW3toE/Lt4vW/Jqga7LTg9zLp0NfS/tL7/O7Eax9wDLp2e54g= > =V56a > -----END PGP SIGNATURE----- > > -- > You received this message because you are subscribed to the Google > Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- R.I.Pienaar -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
