4.0.1

Bug Fixes

• The ca-cert option works in the env.yml.
  A filename or string value can be used.

4.0.0

Breaking Changes

• apply-changes will no longer reattach when it finds an already running installation.
  to re-enable this feature, provide the --reattach flag.
  This makes the behavior of apply-changes easier to anticipate
  and specify whether applying all changes or applying changes to a particular product.

Features

• config-template now accepts --pivnet-file-glob insstead of --product-file-glob.
  This is to create consistency with the download-product command's naming conventions.
  Thanks to @poligraph for the PR!

3.2.2

Bug Fixes

• staged-config will now work again for Ops Manager versions <= 2.3.
  This solves issue #419

3.2.1

Bug Fixes

• configure-director now will configure VM Extensions before setting Resource Config.
  This fixes issue #411

3.2.0

Features

• expiring-certificates command was added.
  This command returns a list of certificates
  from an Ops Manager
  expiring within a specified (--expires-within/-e) timeframe.
  Default: "3m" (3 months)
  Root CAs cannot be included in this list until Ops Manager 2.7.

• configure-product and staged-config now have support for the /syslog_configurations endpoint.
  This affects tiles, such as the Metrics tile,
  that do not return these properties nested in the product-properties section.
  This provides a solution for issue 331.
  An example of this inside of your product config:

  syslog-properties:
    address: example.com
    custom_rsyslog_configuration: null
    enabled: true
    forward_debug_logs: false
    permitted_peer: null
    port: "4444"
    queue_size: null
    ssl_ca_certificate: null
    tls_enabled: false
    transport_protocol: tcp

• generate-certificate can now accept multiple --domains | -d flags.
  Comma separated values can be passed with a single --domains | -d flag,
  or using a --domains | -d flag for each value. Thanks to @jghiloni for the PR!
  Example:

    om -e env.yml generate-certificate -d "example1.com" --domains "example2.com" \
       -d "example3.com,*.example4.com" --domains "example5.com,*.example6.com"

• product-metadata has been added to replace tile-metadata.
  This was done to increase naming consistency.
  Both commands currently exist and do exactly the same thing.
  Thank you @jghiloni for the PR!

• config-template now supports the --exclude-version flag.
  If provided, the command will exclude the version directory in the --output-directory tree.
  The contents will with or without the flag will remain the same.
  Please note including the --exclude-version flag
  will make it more difficult to track changes between versions
  unless using a version control system (such as git).
  Thanks to @jghiloni for the PR!

• config-template supports --pivnet-disable-ssl to skip SSL validation.

• When interacting with an OpsManager, that OpsManager may have a custom CA cert.
  In the global options --ca-cert has been added to allow the usage of that custom CA cert.
  The value of --ca-cert can be a file or command line string.

Bug Fix

• When using config-template or download-product,
  the --pivnet-skip-ssl is honored when capturing the token.

Deprecation Notices

• tile-metadata has been deprecated in favor of product-metadata.
  This was done to increase naming consistency.
  Both commands currently exist and do exactly the same thing.
  The tile-metadata command will be removed in a future release.

3.1.0

Features

• TLS v1.2 is the minimum version supported when connecting to an Ops Manager

• config-template now will provide required-vars in addition to default-vars.

• config-template will define vars with an _ instead of a /.
  This is an aesthetically motivated change.
  Ops files are denoted with /,
  so changing the vars separators to _ makes this easier to differentiate.

• config-template output product-default-vars.yml has been changed to default-vars.yml

• staged-config includes the property max_in_flight will be included
  in the resource-config section of a job.

• configure-product can set the property max_in_flight
  in the resource-config section of a job.

  The legal values are:

  • an integer for the number of VMs (ie 2)
  • a percentage of 1-100 (ie 20%)
  • the default value specified in tile (default)
    For example,

  resource-config:
    diego_cells:
      instances: 10
      max_in_flight: 10

3.0.0

Features

• pivnet-api-token is now optional in download-product
  if a source is defined. Thanks to @vchrisb for the PR!
• configure-authentication, configure-ldap-authentication, and configure-saml-authentication
  can create a UAA client on the Ops Manager vm.
  The client_secret will be the value provided to this option precreated-client-secret.
• add support for NSX and NSXT in Ops Manager 2.7+

Breaking Changes

• remove --skip-unchanged-products from apply-changes
  This option has had issues with consistent successful behaviour.
  For example, if the apply changes fails for any reason, the subsequent apply changes cannot pick where it left off.
  This usually happens in the case of errands that are used for services.

  We are working on scoping a selective deploy feature that makes sense for users.
  We would love to have feedback from users about this.

• remove revert-staged-changes
unstage-product will revert the changes if the tile has not been installed.
  There is currently no replacement for this command,
  however, it was not working for newer versions of Ops Manager, and did nothing.
  This resolves issue #399

Bug Fix

• apply-changes will error with product not found if that product has not been staged.
• upload-stemcell now accepts --floating false in addition to floating=false.
  This was done to offer consistency between all of the flags on the command.
• configure-director had a bug in which iaas_configurations could not be set
  on AWS/GCP/Azure because "POST" was unsupported for these IAASes
  (Multiple IAAS Configurations only work for vSphere and Openstack).
  configure-director will now check if the endpoint is supported.
  If it is not supported, it will construct a payload, and selectively configure
  iaas_configuration as if it were nested under properties-configuration.
  The behavior of this command remains the same.
  IAAS Configuration may still be set via iaas_configurations OR properties.iaas_configuration

2.0.1

Was a release to make sure that brew upgrade works.

2.0.0

2.0.0

Features

• configure-ldap-authentication and configure-saml-authentication will create a bosh admin client by default.
  This can be disabled by adding --skip-create-bosh-admin-client.
  This is supported in OpsManager 2.4+.
• configure-ldap-authentication and configure-saml-authentication can create a UAA client on the Ops Manager vm.
  The client_secret will be the value provided to this option precreated-client-secret.
  This is supported in OpsManager 2.5+.
• A homebrew formula has been added!
  It should support both linux and mac brew.
  Since, we don't have our own tap, we've used a simpler method:

  brew tap pivotal-cf/om https://github.com/pivotal-cf/om
  brew install om

Bug Fixes

• The order of vm types and resources was being applied in the correct order.
  Now vm types will be applied then resources, so that resource can use the vm type.
• When using bosh-env, a check is done to ensure the SSH private key exists.
  If does not the command will exit 1.
• config-template will enforce the default value for a property to always be configurable: false.
  This is inline with the OpsManager behaviour.

Breaking Change

• The artifacts on the Github Release include .tar.gz (for mac and linux) and .zip (windows) for compression.
  It also allows support for using goreleaser (in CI) to create other package manager artifacts -- brew.
  This will break globs that were permissive. For example *linux*, will download the binary and the .tar.gz.
  Our semver API declaration has been updated to reflect this.

1.2.0

Features

• Both om configure-ldap-authentication
  and om configure-saml-authentication
  will now automatically
  create a BOSH UAA admin client as documented here.
  This is only supported in OpsManager 2.4 and greater.
  You may specify the flag skip-create-bosh-admin-client
  to skip creating this client.
  If the command is run for an OpsManager less than 2.4,
  the client will not be created and a warning will be printed.
  However, it is recommended that you create this client.
  For example, your SAML or LDAP may become unavailable,
  you may need to sideload patches to the BOSH director, etc.
  Further, in order to perform automated operations on the BOSH director,
  you will need this BOSH UAA client.
  After the client has been created,
  you can find the client ID and secret
  by following steps three and four found here.
• om interpolate now allows for the -v flag
  to allow variables to be passed via command line.
  Command line args > file args > env vars.
  If a user passes a var multiple times via command line,
  the right-most version of that var will
  be the one that takes priority,
  and will be interpolated.
• om configure-director now supports custom VM types.
  Thanks for the PR @jghiloni!
  Refer to the VM Types Bosh documentation for IaaS specific use cases.
  For further info: configure-director readme.
  Please note this is an advanced feature, and should be used at your own discretion.
• download-product will now return a download-file.json
  if stemcell-iaas is defined but the product has no stemcell.
  Previously, this would exit gracefully, but not return a file.