vagrant-devcommands 0.11.1 → 0.14.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: dd051c66c3c698629e9eeac65aab7f359e7ee230
-  data.tar.gz: e607628cc652b04882a226f7b10def7b32152298
+SHA256:
+  metadata.gz: c87a4a5395ff70331bc828e00f95e4f2bd17b75dbc57561a9a512b2fa94d5402
+  data.tar.gz: ba566aeb333eb32fab9389b979df2f54e2326e0b98cd1beff1e94b07a52a45dd
 SHA512:
-  metadata.gz: 25c8ef756decf39dbce7050799b841e4c4e2aefb4091fd13e12ee221e593efd0434e05e6bfb70b54fc096d473907afe2045d4427960b1878f7f19f2b75fcc1bb
-  data.tar.gz: 8cfa604c43f53e037666378517df766b54ba936b9c428ae89e90fa950d3f2729fc66827c2911ed56e9d494e32234587dc09e935d771afff33d01772b4cc74faa
+  metadata.gz: 18314207fb498117756f3b0b1023c72c75c5c157408895e9d92fcc56f980039f8601f2797ca7013d0c9386f98349566662d4615f5bb329960ac895e49a4814e6
+  data.tar.gz: 6d92ec349743a1658fb1160b45f87c57eaf6785dba47f0c7130f4bf7249d35f40ea67897a6fdbd0b0c1fedf79711bc4d655f95e7650ea8de3e24b859d1aeb451

data/CHANGELOG.md

@@ -1,62 +1,68 @@
 # Changelog
 
+## v0.14.0 (2022-08-23)
+
+- Enhancements
+  - Lambda/Proc values of command scripts are now executed in the instance of the command when running
+  - Lambda/Proc scripts get the parsed argv values as the first (and only) argument unless defined with a zero arity
+
+- Bug fixes
+  - Parameters with a default value configured will now be properly displayed as optional in the detailed command help
+
+## v0.13.0 (2018-07-19)
+
+- Enhancements
+  - Unknown parameters can be catched and used by setting the option `passthru: true` on one of your parameters ([#3](https://github.com/mneudert/vagrant-devcommands/issues/3))
+
+## v0.12.0 (2018-04-21)
+
+- Enhancements
+  - Command parameters can define alias values to be replaced before escaping
+  - Commandfile entries with duplicate names will now issue a warning while still discarding all previous definitions
+  - Commandfile entries with unknown options will issue a warning
+
+- Backwards incompatible changes
+  - Support for the already deprecated configuration parameter `:box` has been removed
+
 ## v0.11.1 (2017-10-04)
 
 - Bug fixes
-  - The machine of a command alias definition is now correctly preferred over
-    the machine of the command definition
+  - The machine of a command alias definition is now correctly preferred over the machine of the command definition
 
 ## v0.11.0 (2017-10-02)
 
 - Enhancements
-  - Command aliases can be used to provide multiple ways to call a single
-    command including automatically populated arguments
+  - Command aliases can be used to provide multiple ways to call a single command including automatically populated arguments
   - Commands can define if they need a tty by using the new `:tty` option
 
 - Backwards incompatible changes
-  - By default a command does not use a tty. This potentially breaks commands
-    requiring one, e.g. a mysql console command
+  - By default a command does not use a tty. This potentially breaks commands requiring one, e.g. a mysql console command
 
 ## v0.10.1 (2017-08-08)
 
 - Bug fixes
-  - Vagrant introduced a tty flag for ssh command execution in version `1.9.6`.
-    This broke some commands requiring an interactive terminal
-    (like a mysql client). This flag is now permanently active to restore the
-    function of these commands until the next regular release introduces a
-    full per command tty configuration
+  - Vagrant introduced a tty flag for ssh command execution in version `1.9.6`. This broke some commands requiring an interactive terminal (like a mysql client). This flag is now permanently active to restore the function of these commands until the next regular release introduces a full per command tty configuration
 
 ## v0.10.0 (2017-07-02)
 
 - Enhancements
-  - Command alternatives provided by the "did-you-mean" feature no longer
-    display the full command list (help)
-  - Depending on the internal scoring multiple alternative commands
-    will be presented instead of a full command list (help)
-  - Minimal data for shell completion is available via the internal
-    `completion-data` command
+  - Command alternatives provided by the "did-you-mean" feature no longer display the full command list (help)
+  - Depending on the internal scoring multiple alternative commands will be presented instead of a full command list (help)
+  - Minimal data for shell completion is available via the internal `completion-data` command
   - Parameters can limit the values you are allowed to pass in
-  - Spaces in chain/command names are now officially disallowed. Those
-    would have always been broken anyways, but now there is a nice message
-    and the commands are excluded from the various listings
+  - Spaces in chain/command names are now officially disallowed. Those would have always been broken anyways, but now there is a nice message and the commands are excluded from the various listings
 
 - Bug fixes
-  - Chain names can no longer conflict with internal commands like `help`
-    or `version`. The respective chain definitions are dropped and a warning
-    is issued
+  - Chain names can no longer conflict with internal commands like `help` or `version`. The respective chain definitions are dropped and a warning is issued
 
 ## v0.9.0 (2017-05-20)
 
 - Enhancements
   - Every command in a chain can specify the machine to be used
-  - If an unknown command is requested a possible alternative
-    is suggested based on the calculated
-    [Jaro-Winkler distance](https://en.wikipedia.org/wiki/Jaro%E2%80%93Winkler_distance)
+  - If an unknown command is requested a possible alternative is suggested based on the calculated [Jaro-Winkler distance](https://en.wikipedia.org/wiki/Jaro%E2%80%93Winkler_distance)
 
 - Deprecations
-  - The configuration parameter `:box` has been renamed to `:machine` to
-    match the vagrant naming. Support for the old configuration will be
-    dropped in a future version
+  - The configuration parameter `:box` has been renamed to `:machine` to match the Vagrant naming. Support for the old configuration will be dropped in a future version
 
 ## v0.8.0 (2017-04-19)
 
@@ -67,14 +73,12 @@
 ## v0.7.2 (2017-03-12)
 
 - Bug fixes
-  - Machine names passed via argv are properly detected and used
-    ([#1](https://github.com/mneudert/vagrant-devcommands/pull/1))
+  - Machine names passed via argv are properly detected and used ([#1](https://github.com/mneudert/vagrant-devcommands/pull/1))
 
 ## v0.7.1 (2017-02-15)
 
 - Bug fixes
-  - Wrapping of optional parameters should now properly be done only if
-    at least an empty string is defined as a default value
+  - Wrapping of optional parameters should now properly be done only if at least an empty string is defined as a default value
 
 ## v0.7.0 (2016-09-26)
 
@@ -87,16 +91,12 @@
 - Enhancements
   - Command usage now displays the correct parameter syntax
   - Command usage always displays mandatory parameters before optional ones
-  - Error output (e.g. "missing Commandfile") is now printed using
-    the configured ui class (allows colored output)
-  - Global commands can be defined using a file
-    named `.vagrant.devcommands` located under `Dir.home()`
+  - Error output (e.g. "missing Commandfile") is now printed using the configured ui class (allows colored output)
+  - Global commands can be defined using a file named `.vagrant.devcommands` located under `Dir.home()`
   - Invalid parameters are displayed in the error message
   - Missing parameters are displayed in the error message
-  - Parameter wrapping is only done if a value is passed
-    or a default (at least empty string) is configured
-  - Warnings about using internal command names or missing scripts are now
-    printed using the configured ui class (allows colored output)
+  - Parameter wrapping is only done if a value is passed or a default (at least empty string) is configured
+  - Warnings about using internal command names or missing scripts are now printed using the configured ui class (allows colored output)
 
 ## v0.5.0 (2016-03-21)
 

data/README.md

@@ -1,7 +1,6 @@
 # Vagrant DevCommands
 
-Runs vagrant commands from a Commandfile.
-
+Runs Vagrant commands from a Commandfile.
 
 ## Usage
 
@@ -32,7 +31,7 @@ Add to a `Commandfile` besides your `Vagrantfile`:
 command 'basic', 'hostname'
 
 command 'with_options',
-  machine: :my_machine,
+  machine: 'my_machine',
   desc: 'executes "hostname" on the machine "my_machine"',
   script: 'hostname',
   tty: true,
@@ -46,28 +45,24 @@ of the command name using either %{command} or %<command>s.
 eoh
 ```
 
-_Note_: If you are defining literal `%` (percent sign) in your commands you
-have to escape them using a second `%`. For example `date "+%%Y-%%m-%%d"`.
+_Note_: If you are defining literal `%` (percent sign) in your commands you have to escape them using a second `%`. For example `date '+%%Y-%%m-%%d'`.
 
-_Note_: Spaces in command names are not supported. Definitions with spaces will
-be ignored.
+_Note_: Spaces in command names are not supported. Definitions with spaces will be ignored.
 
-_Note_: Please be aware that setting a custom `usage` hides the original usage
-line from the help output.
+_Note_: Please be aware that setting a custom `usage` hides the original usage line from the help output.
 
 #### Commands with Parameters
 
-Passing additional parameters to a command is (minimally) supported using an
-sprintf syntax:
+Passing additional parameters to a command is (minimally) supported using an sprintf syntax:
 
 ```ruby
 command 'with_param',
   parameters: {
     # mandatory parameter with a description
-    p_mandatory: { desc: "mandatory parameter to do... stuff!" },
+    p_mandatory: { desc: 'mandatory parameter to do... stuff!' },
 
     # parameter with default (implies optional)
-    p_default: { default: "always" },
+    p_default: { default: 'always' },
 
     # parameter with escaping rule
     p_escaped: { escape: { '*' => '\\' }},
@@ -76,52 +71,64 @@ command 'with_param',
     p_optional: { optional: true },
 
     # wrapped option value
-    p_wrapped: { wrap: "--and %s wrapped" }
+    p_wrapped: { wrap: '--and %s wrapped' },
+
+    # parameters with aliased values
+    # the aliases are resolved prior to escaping/wrapping/allowance!
+    # aliases are resolved in order of definition (multiple can apply)
+    p_aliased: { aliases: { 'foo' => 'bar' }},
 
     # parameters with a limited set of allowed values
     # the allowed values are checked prior to escaping/wrapping!
     # optional parameters are only validated if given!
-    p_limited: { allowed: ['completely'] }
+    p_limited: { allowed: ['completely'] },
+
+    # you can define a specific parameter to receive
+    # all otherwise unknown parameters and flags
+    p_passthru: { optional: true, passthru: true }
   },
-  script: 'echo %<p_mandatory>s %<p_default>s %<p_escaped>s %<p_optional>s %<p_wrapped>s %<p_limited>s'
+  script: %(
+    echo %<p_mandatory>s \
+         %<p_default>s \
+         %<p_escaped>s \
+         %<p_optional>s \
+         %<p_wrapped>s \
+         %<p_limited>s \
+         %<p_passthru>s
+  )
 ```
 
 This allows you to execute the following command:
 
 ```shell
-# will execute 'echo works always'
+# will execute 'echo "works always"'
 vagrant run with_param --p_mandatory works
 
-# will execute 'echo works always like a charm'
-vagrant run with_param --p_mandatory works --p_optional "like a charm"
+# will execute 'echo "works always like a charm"'
+vagrant run with_param --p_mandatory works --p_optional 'like a charm'
 
-# will execute 'echo works sometimes like a charm --and is wrapped completely'
+# will execute 'echo "works sometimes like a charm --and is wrapped completely"'
 vagrant run with_param \
     --p_mandatory works \
     --p_default sometimes \
-    --p_optional "like a charm" \
-    --p_wrapped is
+    --p_optional 'like a charm' \
+    --p_wrapped is \
     --p_limited completely
 ```
 
-For now a command expecting one or more parameters will fail if the user does
-not provide them. Any arguments exceeding the number used are silently
-discarded.
+For now a command expecting one or more parameters will fail if the user does not provide them. Any arguments exceeding the number used are silently discarded.
 
-Escaping rules are defined as `{ "char_to_escape": "char_to_use_as_escape" }`.
-These are applied prior to interpolation into the command. Regular ruby escaping
-rules apply.
+Escaping rules are defined as `{ 'char_to_escape' => 'char_to_use_as_escape' }`. These are applied prior to interpolation into the command. Regular ruby escaping rules apply.
 
 #### Commands with Flags
 
-Every command can be associated with (by definition optional) flags available
-for later command interpolation:
+Every command can be associated with (by definition optional) flags available for later command interpolation:
 
 ```ruby
 command 'with_flags',
   flags: {
-    f_standard: { desc: "standard flag" },
-    f_valued:   { value: "--f_modified" }
+    f_standard: { desc: 'standard flag' },
+    f_valued:   { value: '--f_modified' }
   },
   script: 'echo "flags: %<f_standard>s"'
 ```
@@ -139,28 +146,46 @@ vagrant run with_flags --f_standard
 vagrant run with_flags --f_valued
 ```
 
-By default a flag gets interpolated as "--#{flagname}". If a value is defined
-this value will be interpolated unmodified.
+By default a flag gets interpolated as `--#{flagname}`. If a value is defined this value will be interpolated unmodified.
 
 #### Commands defined by Lambda/Proc
 
-You can (more or less) dynamically generate your scripts by defining the
-command with a lambda or proc as its script.
+You can (more or less) dynamically generate your scripts by defining the command with a lambda or proc as its script.
 
 ```ruby
 command 'from_lambda', script: lambda { 'echo "lambda works"' }
 command 'from_proc', script: proc { 'echo "proc works"' }
+
+command 'from_lambda_params',
+  parameters: { argv_param: {} },
+  script: lambda { |params|
+    'echo "lambda works: ' + params[:argv_param] + '"'
+  }
+
+command 'from_proc_params',
+  parameters: { argv_param: {} },
+  script: proc { |params|
+    'echo "proc works: ' + params[:argv_param] + '"'
+  }
 ```
 
-These will be evaluated when running the command.
+These will be evaluated when running the command and optionally received the parsed shell arguments when defined with an arity of one.
+
+Every rule from regular scripts (parameters, escaping `%`, ...) still apply.
+
+#### Commands with a TTY ("interactive")
+
+If you have a command that expects some sort of interaction with the user you may need to set the `tty` option for a command:
+
+```ruby
+command 'interactive', tty: true
+```
 
-Every rule from regular scripts (parameters, escaping "%", ...) still apply.
+This allows full interaction with programs like `irb` or `mysql`.
 
 ### Global Command Definitions
 
-To have commands available even wihout a `Commandfile` you can define the
-globally. To do this just create a file named `.vagrant.devcommands` in your
-`$HOME` directory.
+To have commands available even wihout a `Commandfile` you can define the globally. To do this just create a file named `.vagrant.devcommands` in your `$HOME` directory.
 
 You can use this command to find the correct path if unsure:
 
@@ -191,20 +216,15 @@ eoh
 
 The configured commands will be executed in the order defined.
 
-If one or more of your commands requires parameters all of them have to be
-passed to the chain execution.
+If one or more of your commands requires parameters all of them have to be passed to the chain execution.
 
-By default a chain breaks upon the first non-zero return value of any
-configured command. To deactivate this behaviour you can set `:break_on_error`
-to `false`. Any value other than `false` will stick to the default.
+By default a chain breaks upon the first non-zero return value of any configured command. To deactivate this behaviour you can set `:break_on_error` to `false`. Any value other than `false` will stick to the default.
 
-_Note_: Spaces in command names are not supported. Definitions with spaces will
-be ignored.
+_Note_: Spaces in command names are not supported. Definitions with spaces will be ignored.
 
 #### Chain Definitions with Pre-Defined Parameters
 
-If required you can modify the arguments given to each chain element by setting
-additional/custom argv values for a single chain element:
+If required you can modify the arguments given to each chain element by setting additional/custom argv values for a single chain element:
 
 ```ruby
 command 'chainecho',
@@ -222,16 +242,14 @@ chain 'my_customized_chain',
 Running the chain will execute the following commands:
 
 ```shell
-> vagrant run my_customized_chain --first="initial" --second="initial"
+> vagrant run my_customized_chain --first='initial' --second='initial'
 
-vagrant run chainecho --first="param" --second="initial"
-vagrant run chainecho --first="initial" --second="initial"
-vagrant run chainecho --first="param" --second="param"
+vagrant run chainecho --first='param' --second='initial'
+vagrant run chainecho --first='initial' --second='initial'
+vagrant run chainecho --first='param' --second='param'
 ```
 
-By default every command will be executed using the machine defined by the
-command itself or the only one available. You can, however, run the complete
-chain against a specific machine using `vagrant run your_machine your_chain`.
+By default every command will be executed using the machine defined by the command itself or the only one available. You can, however, run the complete chain against a specific machine using `vagrant run your_machine your_chain`.
 
 #### Chain Definitions with Specific Machines
 
@@ -259,13 +277,11 @@ vagrant run secondary chainhost
 vagrant run tertiary chainhost
 ```
 
-This configuration can itself be modified by passing a machine name to run
-all chain commands on using  using `vagrant run your_machine your_chain`.
+This configuration can itself be modified by passing a machine name to run all chain commands on using  using `vagrant run your_machine your_chain`.
 
 ### Abort Parsing inside Commandfile
 
-If you, for whatever reasons, want to abort further parsing of a `Commandfile`
-you can simple return from it:
+If you, for whatever reasons, want to abort further parsing of a `Commandfile` you can simple return from it:
 
 ```ruby
 command 'foo', script: 'foo'
@@ -280,16 +296,13 @@ return if v_cur < v_min
 command 'bar', script: 'bar'
 ```
 
-This example leads to the command `bar` not being available if the currently
-installed plugin has a version below `1.3.3.7`.
+This example leads to the command `bar` not being available if the currently installed plugin has a version below `1.3.3.7`.
 
-Please be aware that returning from a global commandfile completely skips
-evaluating a local one.
+Please be aware that returning from a global commandfile completely skips evaluating a local one.
 
-### Experimental: Command Alias Definitions
+### Command Alias Definitions
 
-For commands you want to keep generic but often call with a specific set of
-parameter values you can define an alias:
+For commands you want to keep generic but often call with a specific set of parameter values you can define an alias:
 
 ```ruby
 command 'customecho',
@@ -307,9 +320,7 @@ I get displayed when running "vagrant run help aliasecho".
 eoh
 ```
 
-The setting `command` is required, the other options `argv` and `machine` are
-optional and used for the actual customization. Any argument configured will
-take precedence over the value given to `vagrant run` itself.
+The setting `command` is required, the other options `argv` and `machine` are optional and used for the actual customization. Any argument configured will take precedence over the value given to `vagrant run` itself.
 
 ### Experimental: Shell Completion
 
@@ -323,35 +334,38 @@ vagrant run completion-data
 vagrant run completion-data my-command
 ```
 
-
 ## Notes for Windows Users
 
 ### SSH
 
-If you are using this plugin on a Windows host system, please make sure your
-regular `vagrant ssh [machine]` succeeds. In some cases you may need to add the
-`ssh.exe` (e.g. from a git installation) manually to your `%PATH%`.
+If you are using this plugin on a Windows host system, please make sure your regular `vagrant ssh [machine]` succeeds. In some cases you may need to add the `ssh.exe` (e.g. from a git installation) manually to your `%PATH%`.
 
 ### Command Definition
 
-When using multi-line commands you probably need to define your command using
-a sigil notation like the following:
+When using multi-line commands you probably need to define your command using a sigil notation like the following:
 
 ```ruby
 command 'long_running_task',
   script: %(cd /path/to/somewhere \
-                && echo "starting long running task" \
+                && echo 'starting long running task' \
                 && ./long_running_task.sh \
-                && echo "finished long running task")
+                && echo 'finished long running task')
 ```
 
-Using a quote delimited command definition might otherwise result in not that
-helpful error messages about a bad shell command.
+Using a quote delimited command definition might otherwise result in not that helpful error messages about a bad shell command.
+
+It might also help to double check the line endings in your Commandfile are set unix-style (`\n`) and not windows-style (`\r\n`) if you get errors when running your commands.
 
-It might also help to double check the line endings in your Commandfile are set
-unix-style (`\n`) and not windows-style (`\r\n`) if you get errors when running
-your commands.
+## Development
 
+You can always install the plugin directly from source:
+
+```shell
+gem build vagrant-devcommands.gemspec
+
+vagrant plugin uninstall vagrant-devcommands
+vagrant plugin install vagrant-devcommands-x.x.x.dev.gem
+```
 
 ## License
 

data/lib/vagrant/devcommands/command.rb

@@ -1,8 +1,10 @@
+# frozen_string_literal: true
+
 module VagrantPlugins
   module DevCommands
     # Defines the executable vagrant command
     class Command < Vagrant.plugin(2, :command)
-      I18N_KEY = 'vagrant_devcommands.'.freeze
+      I18N_KEY = 'vagrant_devcommands.'
 
       def self.synopsis
         synopsis = VagrantPlugins::DevCommands::SYNOPSIS
@@ -19,8 +21,6 @@ module VagrantPlugins
       def execute
         return 127 unless read_commandfile
 
-        deprecated_box_config?
-
         command = Util.argv_command(@argv, @env)
 
         return 127 unless non_empty?(command)
@@ -47,12 +47,6 @@ module VagrantPlugins
         @registry.available?(command)
       end
 
-      def deprecated_box_config?
-        return unless @registry.commands.values.any?(&:deprecated_box_config)
-
-        Messages.deprecated_box_config(&@env.ui.method(:warn))
-      end
-
       def display_alternatives(command)
         alternatives = Util.did_you_mean(command, @registry)
         alternatives = alternatives.select { |_k, v| v > 0.8 }
@@ -60,15 +54,15 @@ module VagrantPlugins
         return false if alternatives.empty?
 
         if alternatives.length == 1
-          display_error(I18n.t("#{I18N_KEY}.did_you_mean_single"), true)
+          display_error(I18n.t("#{I18N_KEY}.did_you_mean_single"), pre_ln: true)
         else
-          display_error(I18n.t("#{I18N_KEY}.did_you_mean_multi"), true)
+          display_error(I18n.t("#{I18N_KEY}.did_you_mean_multi"), pre_ln: true)
         end
 
         alternatives.sort.each { |(k, _v)| display_error("        #{k}") }
       end
 
-      def display_error(msg, pre_ln = false, post_ln = false)
+      def display_error(msg, pre_ln: false, post_ln: false)
         @env.ui.error '' if pre_ln
         @env.ui.error msg
         @env.ui.error '' if post_ln
@@ -104,7 +98,7 @@ module VagrantPlugins
 
         runner.run(runnable)
       rescue RuntimeError => e
-        display_error(e.message, false, true)
+        display_error(e.message, post_ln: true)
         run_internal('help', [command])
 
         nil

data/lib/vagrant/devcommands/commandfile/modeler.rb

@@ -1,3 +1,5 @@
+# frozen_string_literal: true
+
 module VagrantPlugins
   module DevCommands
     class Commandfile
@@ -33,9 +35,7 @@ module VagrantPlugins
           options        = { script: options } unless options.is_a?(Hash)
           options[:name] = name
 
-          unless valid_script?(options[:script])
-            raise ArgumentError, 'command_no_script'
-          end
+          raise ArgumentError, 'command_no_script' unless valid_script?(options[:script])
 
           VagrantPlugins::DevCommands::Model::Command.new(options)
         end

data/lib/vagrant/devcommands/commandfile/reader.rb

@@ -1,3 +1,5 @@
+# frozen_string_literal: true
+
 module VagrantPlugins
   module DevCommands
     class Commandfile
@@ -17,8 +19,8 @@ module VagrantPlugins
           local  = @commandfile.path
 
           contents = ''
-          contents += "\n" + global.read unless global.nil?
-          contents += "\n" + local.read unless local.nil?
+          contents += "\n#{global.read}" unless global.nil?
+          contents += "\n#{local.read}" unless local.nil?
 
           instance_eval(contents)
 
@@ -29,24 +31,24 @@ module VagrantPlugins
 
         def chain(name, options = nil)
           @entries << {
-            type:    :chain,
-            name:    name.to_s,
+            type: :chain,
+            name: name.to_s,
             options: options
           }
         end
 
         def command(name, options = nil)
           @entries << {
-            type:    :command,
-            name:    name.to_s,
+            type: :command,
+            name: name.to_s,
             options: options
           }
         end
 
         def command_alias(name, options = nil)
           @entries << {
-            type:    :command_alias,
-            name:    name.to_s,
+            type: :command_alias,
+            name: name.to_s,
             options: options
           }
         end

data/lib/vagrant/devcommands/commandfile.rb

@@ -1,3 +1,5 @@
+# frozen_string_literal: true
+
 require 'pathname'
 
 module VagrantPlugins

data/lib/vagrant/devcommands/help_printer/chain.rb

@@ -1,9 +1,11 @@
+# frozen_string_literal: true
+
 module VagrantPlugins
   module DevCommands
     module HelpPrinter
       # Prints help for a command chain
       class Chain
-        I18N_KEY = 'vagrant_devcommands.internal.help'.freeze
+        I18N_KEY = 'vagrant_devcommands.internal.help'
         UTIL     = VagrantPlugins::DevCommands::Util
         MESSAGES = VagrantPlugins::DevCommands::Messages
 
@@ -20,9 +22,9 @@ module VagrantPlugins
         private
 
         def body(help)
-          return message(:chain_no_help, true) if help.nil?
+          return message(:chain_no_help, pre_ln: true) if help.nil?
 
-          info(help.strip, true)
+          info(help.strip, pre_ln: true)
         end
 
         def chain_help_line(cmd)
@@ -32,7 +34,7 @@ module VagrantPlugins
         end
 
         def commands(chain)
-          info('Chained commands (in order):', true)
+          info('Chained commands (in order):', pre_ln: true)
 
           chain.commands.each do |cmd|
             info(UTIL.padded_columns(0, chain_help_line(cmd)))
@@ -50,12 +52,12 @@ module VagrantPlugins
           info(I18n.t("#{I18N_KEY}.usage", what: usage))
         end
 
-        def info(msg, pre_ln = false)
+        def info(msg, pre_ln: false)
           @env.ui.info '' if pre_ln
           @env.ui.info msg
         end
 
-        def message(msg, pre_ln = false)
+        def message(msg, pre_ln: false)
           if pre_ln
             MESSAGES.pre_ln(msg, &@env.ui.method(:info))
           else