0.20.0

Bug fixes:

• JSON responses from om curl will no longer be interpolated.
• No longer attempts to create availability zones for IAASes that don't support them, like Azure.

0.19.0

New in this release:

• Running configure-bosh after your director has been deployed will no longer result in a cryptic error. om will detect that the director is already deployed and provide a nice warning message indicating that it is skipping this step.
• For commands that require it, the password can be provided by setting the OM_PASSWORD environment variable instead of using the --password flag.
• The om errands command will list "post-deploy" errands. We will be adding "pre-delete" errand support in a future release.
• When running om apply-changes and "re-attaching" to an running installation, the installation ID and start time will now be printed out before the logs display.
• You can now use --client-id and --client-secret flags to authenticate if you have a UAA client instead of a username and password.

Bug fixes:

• Setting internet_connected to false will actually stick when using the configure-product command with the --product-resources flag.
• Some HTTP requests that result in a "dial tcp: i/o timeout" error will now be retried. Hopefully this will make long-running commands a bit more stable.
• The om import-installation command will no longer "peg" your CPU.

0.18.0

New in this release:

Bug Fixes

• Fixes a bug where providing the --help flag for a command that also requires the --target flag would produce an error.
• Fixes ignore_warnings so that it is now a quoted string instead of a json bool
• Fixes #41 so you can now re-attach to a running deletion

New Features

• Highly Experimental support for configuring Openstack environments
• Allows for bosh configuration of AWS networks

Provided the ability for an operator to configure their bosh director.

The syntax below is now supported for --resource-configuration when calling the configure-bosh command:

{
    "director": {
        "instance_type": {
            "id": "m1.medium"
        },
        "persistent_disk": {
            "size_mb": "20480"
        },
        "internet_connected": true,
        "elb_names": ["my-elb"]
    },
    "compilation": {
        "instances": 1,
        "instance_type": {
            "id": "m1.medium"
        },
        "internet_connected": true,
        "elb_names": ["my-elb"]
    }
}

Breaking Changes

We have slightly tweaked the format required for passing network configuration to om this was done to accommodate the way AWS networks work. The iaas_identifier now resides within the subnet object like so:

"subnets": [
  {
    "iaas_identifier": "vpc-subnet-id-2",
    "cidr": "10.0.4.0/22",
    "reserved_ip_ranges": "10.0.4.0-10.0.4.4",
    "dns": "8.8.8.8",
  }
]

The documentation has been updated to reflect this.

0.17.0

New in this release:

• Fixes an issue with product resource configuration on IAASes that do no support attaching public IPs [https://github.com//pull/37]
• Allows proxy information to be provided via environment variables. More details can be found here.

0.16.0

New in this release:

• Fixes an issue that prevented availability zones from being assigned on vSphere. More details can be found in the docs.

0.15.0

Warning This release contains a backward-incompatible change to the structure of the --az-configuration flag in the configure-bosh command. The flag input required a refactoring to enable support for vSphere Director AZ configuration. The primary change is that the input for existing IAASes, like GCP and AWS will change to look like the following:

{
  "availability_zones": [
    {"name": "az-1"},
    {"name": "az-2"}
  ]
}

New in this release:

• Support for configuring availability zones on vSphere Directors. More details can be found in the docs.

0.14.0

New in this release:

• --path is now a required argument in the curl command.
• For commands that require a target, not specifying the --target global flag will produce an error.
• The logging for configure-product will now provide some more insight into what exactly is being configured.
• The available-products command will list the set of available products on an Ops Manager.
• stage-product behaves correctly when staging a new version of a product that has never been deployed.
• Commands that provide feedback about time elapsed since some event will do so with a more human-friendly output.

0.13.0

New in this release:

• revert-staged-changes will now reset any staged changes back to their last known good settings.
• delete-installation does not error when there is no installation to delete.

0.12.0

New in this release:

• configure-bosh now allows you to configure a BOSH director tile on your Ops Manager. See the documentation here for more info.

0.11.0

New in this release:

• delete-unused-products will allow you go get rid of products that are not being used by your Ops Manager.
• import-installation will now wait until the UAA has come up to complete.
• commands now all support --help, -help, and -h flags for printing command-specific help.
• apply-changes will now "re-attach" to an ongoing installation when one is already in progress.
• apply-changes is now capable of ignoring warnings if any are found before deployment.
• upload-product will check to see if a product has already been uploaded before uploading it again.
• Fixes a bug in export-installation that incorrectly read the exported installation zip file into memory and would cause memory-constrained environments to error.