Jira (PUP-6660) cached catalogs setting not respected when --test is specified

[Mike Smith (JIRA)]

Title: Message Title

Mike Smith commented on PUP-6660   Re: cached catalogs setting not respected when --test is specified Ryan Coleman Looking at this from the user experience perspective, we have essentially told them (historically) "the default command line way to invoke a puppet run is puppet agent -t, and this will respect cached catalog settings." Pre 4.6.0 in cached catalog mode: Default command puppet agent -t Non-Default command puppet agent -t --no-use_cached_catalog Post 4.6.0 in cached catalog mode: Default command puppet agent -t --no-daemonize --onetime --verbose --no-usecacheonfailure --detailed-exitcodes --no-splay --show_diff Non-Default command puppet agent -t In this case default command means the standard user command they would run to start puppet as configured. This feels like a breaking change from a user experience here. Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.