> (Copied from github comments) > > Daniel, > > I’m in agreement with Nan. > > We do make claims that puppet apply is a “first class citizen” and community > members like Jordan Sissel heavily rely on puppet apply being feature > complete with puppet agent. > > Furthermore, puppet apply is more suitable for situations like Vagrant where > a full master is not avaialable or necessary. > > Finally, as we integrate more with MCollective, the classes.txt file becomes > ever more important for filtering. > > For these reasons I think we should still write the file and we should write > it to the same file the agent writes to by default.
So, I think those are compelling use cases, and we should *enable* parity, but not by default. Would a compromise that added a configuration option for `apply` mode, defaulting to `classes_from_apply.txt` or so, and allowing you to manually configure it to the default location satisfy your needs? That way people who use apply for something small don't lose data out of the box, but folks who do want the capability can enable it? One configuration bit later, and it is even transparent. I would have no trouble with that approach. -- 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.
