Jira (PUP-2243) Using a prefix of a setting on the CLI doesn't work nor fail

[Andy Parker (JIRA)]

Title: Message Title

Andy Parker created an issue   Puppet / PUP-2243 Using a prefix of a setting on the CLI doesn't work nor fail Issue Type: Bug Affects Versions: 3.4.3 Assignee: Unassigned Created: 14/Apr/14 2:28 PM Priority: Normal Reporter: Andy Parker I tried this out on 3.4.3, but I'm pretty certain that it goes back much further. The problem is that on the command line you can specify a prefix of a setting (such as order instead of ordering), but if that is done the setting does not get set. It also does not raise an error (follow tests done on a development branch). Setting taking effect > be puppet apply -e 'notice($::settings::certname)' --certname foo Warning: Could not retrieve fact fqdn Notice: Scope(Class[main]): foo Notice: Compiled catalog for foo in environment production in 0.43 seconds Notice: Finished catalog run in 0.04 seconds Setting prefix used. Does not take effect also does not error > be puppet apply -e 'notice($::settings::certname)' --certna foo Warning: Could not retrieve fact fqdn Notice: Scope(Class[main]): aparker Notice: Compiled catalog for aparker in environment production in 0.41 seconds Notice: Finished catalog run in 0.04 seconds Rejects unknown setting > be puppet apply -e 'notice($::settings::certname)' --certnax foo Error: Could not parse application options: invalid option: --certnax I would expect either --certna to work just like --certname or to produce an error like --certnax Add Comment   This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.