summaryrefslogtreecommitdiffstats
path: root/examples/code
diff options
context:
space:
mode:
authorDaniel Pittman <daniel@puppetlabs.com>2011-04-27 14:21:42 -0700
committerDaniel Pittman <daniel@puppetlabs.com>2011-04-28 14:50:12 -0700
commit69e4b1c5c024f4e6087054a7d8e77d30cacc62c8 (patch)
tree8286e2f2ea9090f8e60fd30d55cc7020574673f8 /examples/code
parent351b6fc5327baf8f2339fed04c3a8e54280fc394 (diff)
downloadpuppet-69e4b1c5c024f4e6087054a7d8e77d30cacc62c8.tar.gz
puppet-69e4b1c5c024f4e6087054a7d8e77d30cacc62c8.tar.xz
puppet-69e4b1c5c024f4e6087054a7d8e77d30cacc62c8.zip
(#7122) Enforce call arity on actions in the CLI wrapper.
We had a problem, previously, in the generic translation of command line arguments to Ruby method calls: we could mistake the options, added by the CLI wrapper, for a positional argument to the action method. This was caused by a combination of factors, but primarily that the wrapper methods for actions are designed to present a friendly, helpful Ruby API for internal use. Consequently, they have a default value if you don't wish to pass options. Unfortunately, this meant that the options that the CLI *always* passed could be treated as a positional argument instead, and the default set of options added to the back of the call. To resolve this we now check the number of positional arguments in the CLI wrapper, and raise an exception if they are mismatched. This makes the generic CLI handling do the right thing in adapting the command line arguments to the Ruby API. (As an aside, we would have had a similar-but-different failure mode if we type-checked positional arguments: these calls would have failed with an invalid argument validation error.) Reviewed-By: Max Martin <max@puppetlabs.com>
Diffstat (limited to 'examples/code')
0 files changed, 0 insertions, 0 deletions