0.8.0

Another new feature and some networking timeout configurability:

• om delete-installation

om delete-installation

This command can be invoked as follows:

$ om --target https://opsman.example.com \
     --username "some-username" \
     --password "some-password" \
     delete-installation'

Network timeout configuration

A new global flag has been added to om to allow users to set more relaxed networking timeout configurations. This is helpful if you are working on a slow network, or are transferring very large files between your local machine and the OpsManager. The flag is --request-timeout and takes an integer argument for the number of seconds to wait before giving up on a response to a request. The default value is 1800 (30 minutes).

0.7.0

Two more awesome features now added to om:

• om curl
• om configure-product

om curl

This command can be invoked as follows:

$ om --target https://opsman.example.com \
     --username "some-username" \
     --password "some-password" \
     curl \
       --path /api/v0/disk_types \
       --request PUT \
       --data '{ "disk_types": [ { "size_mb": 999 } ] }'

om configure-product

This command can be invoked as follows:

$ om --target https://opsman.example.com \
     --username "some-username" \
     --password "some-password" \
    configure-product \
       --product-name cf \
       --product-properties '{ ".ha_proxy.skip_cert_verify": { "value": true } }'

The JSON payload provided to the product properties argument should match the values passed to the API for OpsManager.

Note: configure-product does not have support for configuring networks or resource configuration. Those features will be coming in a future release.

0.6.0

Three more awesome features now added to om:

• om stage-product
• om apply-changes
• om import-installation

om stage-product

This command can be invoked as follows:

$ om --target https://opsman.example.com \
     --username "some-username" \
     --password "some-password" \
     stage-product \
       --product-name elastic-runtime
       --version 1.8.9

om import-installation

$ om --target https://opsman.example.com \
     import-installation \
       --installation /path/to/export.tgz
       --decryption-passphrase some-password

Please note, this is an unauthenticated command and must be run against a fresh Ops Manager (no configuration).

om apply-changes

$ om --target https://opsman.example.com \
     --username "some-username" \
     --password "some-password" \
     apply-changes

Nothing magical here, just apply all of the changes.

we'll see you bright and early next release.

0.5.0

Two beautiful features in one highly anticipated release (it could be the hottest thing this fall). This release introduces two commands to the om stable:

• om upload-product
• om export-installation

om upload-product

This command can be invoked as follows:

$ om --target https://opsman.example.com \
     --username "some-username" \
     --password "some-password" \
     upload-product \
       --product /path/to/product.tgz

Just like the stemcell before it, a product tgz will be checked to make sure it is non-zero. At present, there is no check that duplicate products are being uploaded. This will be updated in the next release.

om export-installation

$ om --target https://opsman.example.com \
     --username "some-username" \
     --password "some-password" \
     export-installation \
       --output-file /path/to/out.tgz

Export your installation in tgz format. Don't forget that this installation is encrypted! The file will be overwritten if it already exists, please use caution.

see you next release!

0.4.0

New for this release we have added the ability to upload a stemcell. This also introduces two brand new global flags --username and --password so that an oauth token can be acquired.

om upload-stemcell

This command can be invoked as follows:

$ om --target https://opsman.example.com \
     --username "some-username" \
     --password "some-password" \
     upload-stemcell \
       --stemcell /path/to/stemcell

The stemcell file will be checked to make sure it actually has content and then immediately uploaded to the Ops Manager. The progress bar will be visible until the Ops Manager has returned a 200 to confirm that the stemcell was uploaded successfully.

om help upload-stemcell

$ om help upload-stemcell
upload-stemcell
This command will upload a stemcell to the target Ops Manager. If your stemcell already exists that upload will be skipped

Usage: om [options] upload-stemcell [<args>]
  -v, --version              bool    prints the om release version (default: false)
  -h, --help                 bool    prints this usage information (default: false)
  -t, --target               string  location of the Ops Manager VM
  -u, --username             string  admin username for the Ops Manager VM
  -p, --password             string  admin password for the Ops Manager VM
  -k, --skip-ssl-validation  bool    skip ssl certificate validation during http requests (default: false)

Command Arguments:
  -s, --stemcell  string  path to stemcell

0.3.0

This release includes the ability to configure the authentication mechanism of a freshly deployed OpsManager. Additionally, it includes enhancements to the om help command, allowing users to view command-specific help information.

om configure-authentication

This command can be invoked as follows:

$ om --target https://opsman.example.com \
     configure-authentication \
       --username admin-username \
       --password admin-password \
       --decryption-passphrase passphrase

Once invoked, the command will setup the internal userstore authentication mechanism with the admin user configured with your provided information. The command cannot be run more than once against a single OpsManager deployment. Subsequent runs of the command will indicate that the authentication mechanism has already been configured, skipping any further configuration.

om help configure-authentication

$ om help configure-authentication
This command helps setup the authentication mechanism for your OpsManager.
The "internal" userstore mechanism is the only currently supported option.

Usage: om [options] configure-authentication [<args>]
  -v, --version              bool    prints the om release version (default: false)
  -h, --help                 bool    prints this usage information (default: false)
  -t, --target               string  location of the OpsManager VM
  -k, --skip-ssl-validation  bool    skip ssl certificate validation during http requests (default: false)

Command Arguments:
  -u, --username                string  admin username
  -p, --password                string  admin password
  -dp, --decryption-passphrase  string  passphrase used to encrypt the installation

0.2.0

Adds help information:

$ om -h
om cli helps you interact with an OpsManager

Usage: om [options] <command> [<args>]
  -v, --version  prints the om release version
  -h, --help     prints this usage information

Commands:
  version  prints the om release version
  help     prints this usage information

0.1.0

Allows the version information to be printed:

$ om -v
v0.1.0

$ om --version
v0.1.0

$ om version
v0.1.0