7.1.2

Bug Fixes

• The nom alias was not apart of the config file block list.

7.1.1

Bug Fixes

• The oauth handler created a client with a request and connection timeout.
  When that timeout occurred and a retry happened (usually in the command logic)
  the HTTP client would be reused.
  The previous timeout would be propagated.
  This will not create a new HTTP client each time.

7.1.0

Features

• om configure-opsman can now set the UAA token expirations and timeouts.
  For example,

  tokens-expiration:
    access_token_expiration: 10
    refresh_token_expiration: 10
    session_idle_timeout: 10

Bug Fixes

• When using a long running command (ie apply-changes) the UAA token could expire.
  Now once the token expires, it will refress with the UAA, so no disruption occurs.

7.0.2

Bug Fixes

• When using the stemcell-heavy in a download-product config file,
  it would error with cannot have an argument error. [#521]

7.0.1

Bug Fixes

• Some of the -c short flags were conflicting with short values.

7.0.0

Breaking Changes

• Because of code changes in om, the long command line flags no longer support single dash assignment.
  For example, if you had been doing:

  om --env env.yml diagnostic-report -format json

  You now have to:

  om --env env.yml diagnostic-report --format json

• Some commands have different short command line flags.
  For example:

  om --env env.yml apply-changes -sdp

  Must now be called like

  om --env env.yml apply-changes -s

  List of changes:

  command	original short	new short
  global	-tr	n/a
  apply-changes	-sdp	-s
  configure-authentication	-dp	-d
  configure-ldap-authentication	-dp	-d
  configure-saml-authentication	-dp	-d
  import-installation	-pi	-p
  upload-product	-pi	-p

Features

• om bosh-env now supports being able to --unset environment variables.
  This can also unset --bosh and --credhub vars only
  when used with the new --unset flag.
  This resolved issue #457.
  Thanks to @iplay88keys for the PR!

• Format of the help command has been changed.
  This is due to a transition to jessevdk/go-flags from pivotal-cf/jhanda

• vm-lifecyle command had been added.
  This command will create, delete, or upgrade the Ops Manager VM.
  For users of Platform Automation
  will recognize this command.
  It is the om equivalent of p-automator.

  Most of these subcommands require the IAAS CLI to be installed.
  These clis are:

  IAAS	Required CLI	Version
  AWS	aws	v1.18.163+
  Azure	az	v2.13.0+
  GCP	gcloud	v315.0.0+
  Openstack	openstack	n/a
  vSphere	govc	0.23.0+

• vm-lifecycle create-vm will create an Ops Manager VM on a given IAAS.
  NOTE: this command requires the relevant IAAS CLI to be installed.

• vm-lifecycle delete-vm will delete an Ops Manager VM on a given IAAS.
  NOTE: this command requires the relevant IAAS CLI to be installed.

• vm-lifecycle export-opsman-config will export an opsman.yml
  (for use in create-vm and delete-vm) for an existing Ops Manager VM.

• vm-lifecycle prepare-tasks-with-secrets modifies a Concourse task to include
  configuration secrets as params.

• vm-lifecycle upgrade-opsman is a command that will call
  delete-vm, create-vm, and import-installation, with additional safeguards
  to prevent accidental deletion of importan Ops Manager VM data.
  This command is idempotent, has strict command line requirements,
  and tracks state via a state file.

6.5.0

Features

• om products has been added.
  This combines the functionality of staged-products, available-products, and deployed-products
  and gives a default view that displays all three.
  This resolved issue #458.
  Thanks to @iplay88keys for the PR!
• om bosh-env now supports the --credhub and --bosh flags.
  If provided, only the vars for the provided flags will be printed.
  Default behavior of printing both sets of vars remains the same.
  This resolved issue #466.
  Thanks to @iplay88keys for the PR!

Deprecation Notices

These deprecations were added to eventually minimize
some of the ever-growing command overhead in om

• deployed-products has been deprecated in favor of om products --deployed
• available-products has been deprecated in favor of om products --available
• staged-products has been deprecated in favor of om products --staged

6.4.2

Bug Fixes

• upload-stemcell when providing --stemcell it always required an absolute path.
  This has been fixed, so any stemcell path can be used.
  Fixed #498.

6.4.1

Bug Fixes

• pending-changes would always fail if installation incomplete, product unconfigured, or stemcell missing
  regardless of whether the --check flag (exit 1 if there are pending changes) was set.
  This has been fixed so that the implied and intended behavior is reflected in the ouput of the command.

6.4.0

Features

• When using stage-product, the --product-version can use the placeholder latest.
  This finds the highest semvered available product (of --product-name) version to stage.
• When using stage-product the config file provided can be any config file,
  just as long as it has product-version and product-name.

Bug Fixes

• tl;dr: Collections are hard.

  We are reverting code for handling collections when updating their values.
  As of recently, we tried to make collection property updating for products more idempotent.
  This required logic to associate collections in a config file with their potential GUID in the already configured product.
  This logic introduced edge cases, which we missed.
  We tried to fix them, but kept running into them.
  We've made the decision to revert the logic to its original state.
  Please see the original issue #207 for more information.