[PDK-408] pdk bundle consumes and rejects option flags meant for bundler subcommands Created: 2017/08/09 Updated: 2017/10/20 Resolved: 2017/10/05
|Project:||Puppet Development Kit|
|Reporter:||Charlie Sharpsteen||Assignee:||David Schmitt|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Epic Link:||PDK v1.2.0|
|Team:||Puppet Developer Experience|
|Method Found:||Needs Assessment|
|Release Notes:||Known Issue|
|Release Notes Summary:|| This only affects powershell. The problem is that the PDK is consuming command line options meant for the subcommand. The work around is to use 'pdk bundle exec' and then type the command you would like to run with its command line options.
DOCS note: this experimental command is not documented in the docs site, so I've added the known issue in the README, where the command is documented.
|QA Risk Assessment:||Needs Assessment|
When run on windows, the pdk bundle command doesn't allow using -- as a separator between pdk option flags and bundler option flags as suggested by pdk help bundle.
1. Instal v0.6.0 of the PDK on a Windows 2012 R2 server.
The command fails with an "illegal option" error:
Bundler options are accepted and passed to the underlying command. This is the behavior of PDK v0.6.0 on CentOS 7:
|Comment by Austin Blatt [ 2017/08/11 ]|
Example work around
pdk bundle install – --binstubs will install binstubs on non-Windows systems. The equivalent workaround command on Windows Powershell is to do pdk bundle exec "bundle install --binstubs"
|Comment by Tim Sharpe [ 2017/08/13 ]|
PowerShell seems to handle `--` differently and strips it out of the command arguments, so it never gets sent through to the ruby process.
If you escape the – in PowerShell style with a single backtick, it works as expected.