4.6.0

Features

• configure-authentication now supports
  the OM_DECRYPTION_PASSPHRASE environment variable.

Bug Fixes

• configure-director now correctly handles when you don't name your iaas_configuration default on vSphere.
  Previously, naming a configuration anything other than default would result in an extra, empty default configuration.
  This closes issue #469.
• Downloading a stemcell associated with a product will try to download the light or heavy stemcell.
  If anyone has experienced the recent issue with download-product
  and the AWS heavy stemcell,
  this will resolve your issue.
  Please remove any custom globbing that might've been added to circumvent this issue.
  For example, stemcall-iaas: light*aws should just be stemcell-iaas: aws now.
• Heavy stemcells could not be downloaded.
  Support has now been added.
  Force download of the heavy stemcell (if available) with the --stemcell-heavy flag.

3.2.3

Bug Fixes

• Downloading a stemcell associated with a product will try to download the light or heavy stemcell.
  If anyone has experienced the recent issue with download-product and the AWS heavy stemcell,
  this will resolve your issue. Please remove any custom globbing that might've been added to
  circumvent this issue. For example, stemcall-iaas: light*aws should just be stemcell-iaas: aws now.

4.5.0

Features

• interpolate now supports the dot notation to reference array values.
  For example,

  $ echo "person: ((people.1))" | om interpolate -c - -l <(echo "people: [Bob, Susie, Diane]")
  person: Susie

4.4.2

Features

• To mitigate confusion, the pivnet-file-glob param for download-product now has an alias of file-glob.
• Included interpolation for the update-ssl-certificate command.
  A test to see if it is valuable to add it to other commands.

4.4.1

Features

• The experimental command product-diff had been renamed bosh-diff and now includes the director diff.
  This includes property, runtime config, cloud config, and CPI config differences.
  When the command is used, it will display the director and all products by default.
  The --director flag can be used to show only the director diff.
  The --product-name flag can be used to show one or more specific products.

  For example, om bosh-diff --director --product-name cf --product-name p-healthwatch
  will show the director, Pivotal Application Service, and Pivotal Healthwatch differences.

4.4.0

Features

• The experimental command product-diff has been added.
  It gets the manifest diff for a specified set of products.
  This might be useful as a sanity review before apply-changes;
  see the detailed documentation for details/provisos.
• config-template now includes the option to use a local product file with --product-path.
  This resolves issue #413.
• apply-changes can for recreate the VMs that will apply with --recreate-vms.
  This is useful for the three-Rs of security,
  to ensure the repaving.

Bug Fixes

• The environment variable OM_VARS_ENV was not enabled on all commands that allows --vars-env.

4.3.0

Features

• We'd like to welcome back the revert-staged-changes command.
  It requires an API endpoint released in Ops Manager versions 2.5.21+, 2.6.13+, or 2.7.2+.
  This now reverts changes like the the equivalant "Revert" button in the UI.
  Appropriate messages and warnings will appear from the command of what action has been taken.

  In v3.0.0, we removed revert-staged-changes because it had stopped working.
  (The necessary Ops Manager API wasn't present, so it was trying to automate
  through the UI - unsuccessfully).

Bug fixes

• Maybe not technically a bug, but:
  some commands you love (pre-deploy-check, staged-config, and staged-director-config)
  no longer have the EXPERIMENTAL tag.
  Nothing has changed with them, we literally just forgot to remove these ages ago.

4.2.1

Bug fixes

• interpolate command now has order precedence when a file or stdin is provided.
  • --config with a file always takes precedence
  • --config - will read directly from STDIN
  • STDIN provided with no --config will use STDIN
• when using --ignore-verifier-warnings with configure-director the HTTP Status 207
  will be ignored when interacting with IAAS endpoints.

4.2.0

Features

• config-template now includes max-in-flight for all resources. (PR: @jghiloni)
• When using configure-product and configure-director,
  the addtional_vm_extensions for a resource will have the following behaviour:
  • If not set in config file, the value from Ops Manager will be persisted.
  • If defined in the config file and an emtpy array ([]), the values on Ops Manager will be removed.
  • If defined in the file with a value (["web_lb"]), these values will be set on Ops Manager.
• configure-authentication, configure-ldap-authentication, and configure-saml-authentication
  now support the --var, --vars-file, and --vars-env flags.
• config-template now supports the --config, --var, --vars-file, and --vars-env flags.
  (PR: @jghiloni)

4.1.0

Features

• download-product supports GCS (Google Cloud Storage)
  for Pivnet download artifacts.

  An example config,

  pivnet-file-glob: "*.tgz"
  pivnet-product-slug: pivotal-telemetry-collector
  product-version: "1.0.1"
  output-directory: /tmp
  source: gcs
  gcs-bucket: some-bucket
  gcs-service-account-json: |
    {account-JSON}
  gcs-project-id: project-id

  This will download the [pivotal-telemetry-collector,1.0.1]telemetry-collector-1.0.1.tgz
  from the some-bucket bucket from the GCS account.

• download-product supports Azure Storage.
  for Pivnet download artifacts.

  pivnet-file-glob: "*.tgz"
  pivnet-product-slug: pivotal-telemetry-collector
  product-version: "1.0.1"
  output-directory: /tmp
  source: azure
  azure-container: pivnet-blobs
  azure-storage-account: some-storage-account
  azure-key: "storage-account-key"

  This will download the [[pivotal-telemetry-collector,1.0.1]telemetry-collector-1.0.1.tgz
  from the pivnet-blobs container
  from the some-storage-account storage account from Azure Storage.

• The commands disable-director-verifiers
  and disable-product-verifiers have been added.
  They allow verifiers that are preventing Apply Changes from succeeding to be disabled.
  This feature should be used with caution,
  as the verifiers can provide useful feedback on mis-configuration.

• When using staged-director-config and configure-director,
  the iaas_configuration_name will be used to assign an IAAS to an availability zone.
  This provides support for multiple iaas configurations on vSphere and Openstack.
  Prior to this, the iass_configuration_guid had to be discovered prior to assigning an availability zone;
  now the name can be used in one step.

• We've also made miscellanious improvements
  to warning and error messages,
  and to documentation.