Add -d/--deployment option to "deploy" command

[drnic]

Similar to #387

-d is listed as a common option for all bosh commands; but it isn't available for deploy:

$ bosh deploy -d ../sslproxy-dfw2-prod/sslproxy-dfw2-prod.yml 
invalid option: -d

$ bosh help
BOSH CLI helps you manage your BOSH deployments and releases.

Usage: bosh [<options>] <command> [<args>]
    -c, --config FILE                Override configuration file. Also can be overridden by BOSH_CONFIG environment variable. Defaults to $HOME/.bosh_config. Override precedence is command-line option, then environment variable, then home directory.
    -C, --cache-dir DIR              Override cache directory
        --[no-]color                 Toggle colorized output
    -v, --verbose                    Show additional output
    -q, --quiet                      Suppress all output
    -n, --non-interactive            Don't ask for user input
    -N, --no-track                   Return Task ID and don't track
    -P, --poll INTERVAL              Director task polling interval
    -t, --target URL                 Override target
    -u, --user USER                  Override username
    -p, --password PASSWORD          Override password
    -d, --deployment FILE            Override deployment

[xoebus]

The --deployment flag is a global flag and so it has to be before the sub command. The command bosh -d manifest.yml deploy should be used for this use case.

[drnic]

Ahhhhh right I forgot thanks.

--

Dr Nic Williams Stark & Wayne LLC - the consultancy for Cloud Foundry http://starkandwayne.com +1 415 860 2185 twitter: drnic

On Fri, Aug 16, 2013 at 4:02 AM, Chris Brown notifications@github.com wrote:

The --deployment flag is a global flag and so it has to be before the sub command. The command bosh -d manifest.yml deploy should be used for this use case.

Reply to this email directly or view it on GitHub: https://github.com/cloudfoundry/bosh/issues/388#issuecomment-22760006

[jfoley]

Closing

@aramprice / @jfoley