Some command line options for omnitruck install.sh not documented

Chef Infra (archive)
1

Ohai Chefs,

not sure if this is the best place to raise this.

While working on a PR for a related issue in Vagrant [0], I noticed
that the -d and -f command line options of the omnitruck
install.sh [1] are not officially documented yet here:
https://docs.chef.io/install_omnibus.html

So what do they do?

  • if neither -d or -f are specified the omnibus package is
    downloaded to a transient temp directory
  • if -d (directory) is specified the omnibus package will be
    downloaded to that directory with its original filename being
    preserved
  • if -f (path to filename) is specified the omnibus package will be
    downloaded to that specific filename

You can find a bit more detailed description in [1].

Mind adding these to the official docs?

Cheers,
Torben

[0] https://github.com/mitchellh/vagrant/issues/4989
[1] https://github.com/opscode/opscode-omnitruck/pull/33

2

Hi,

You can open an issue against GitHub - chef-boneyard/chef-web-docs-2016: DEPRECATED - All The Documentation, I
am sure that James Scott will help you.

Regards,
Krzysztof

On 16 December 2014 at 22:22, Torben Knerr mail@tknerr.de wrote:

Ohai Chefs,

not sure if this is the best place to raise this.

While working on a PR for a related issue in Vagrant [0], I noticed
that the -d and -f command line options of the omnitruck
install.sh [1] are not officially documented yet here:
Chef Software Install Script

So what do they do?

  • if neither -d or -f are specified the omnibus package is
    downloaded to a transient temp directory
  • if -d (directory) is specified the omnibus package will be
    downloaded to that directory with its original filename being
    preserved
  • if -f (path to filename) is specified the omnibus package will be
    downloaded to that specific filename

You can find a bit more detailed description in [1].

Mind adding these to the official docs?

Cheers,
Torben

[0] Chef auto-install: allow for caching of the downloaded Omnibus package · Issue #4989 · hashicorp/vagrant · GitHub
[1] Cache omnibus download by tknerr · Pull Request #33 · chef/omnitruck · GitHub

3

Thanks Krzysztof!

Added the issue here:

Cheers,
Torben

On Tue, Dec 16, 2014 at 11:38 PM, Krzysztof Wilczynski
krzysztof.wilczynski@linux.com wrote:

Hi,

You can open an issue against GitHub - chef-boneyard/chef-web-docs-2016: DEPRECATED - All The Documentation, I
am sure that James Scott will help you.

Regards,
Krzysztof

On 16 December 2014 at 22:22, Torben Knerr mail@tknerr.de wrote:

Ohai Chefs,

not sure if this is the best place to raise this.

While working on a PR for a related issue in Vagrant [0], I noticed
that the -d and -f command line options of the omnitruck
install.sh [1] are not officially documented yet here:
Chef Software Install Script

So what do they do?

  • if neither -d or -f are specified the omnibus package is
    downloaded to a transient temp directory
  • if -d (directory) is specified the omnibus package will be
    downloaded to that directory with its original filename being
    preserved
  • if -f (path to filename) is specified the omnibus package will be
    downloaded to that specific filename

You can find a bit more detailed description in [1].

Mind adding these to the official docs?

Cheers,
Torben

[0] Chef auto-install: allow for caching of the downloaded Omnibus package · Issue #4989 · hashicorp/vagrant · GitHub
[1] Cache omnibus download by tknerr · Pull Request #33 · chef/omnitruck · GitHub