Release 1.0.0 · pivotal-cf/om

om will now follow conventional Semantic Versioning, with breaking changes in major bumps, non-breaking changes for minor bumps, and bug fixes for patches.
delete-installation now has a force flag. The flag is required to run this command quietly, as it was working before. The reason behind this is it was easy to delete your installation without any confirmation.
staged-director-config no longer supports --include-credentials this functionality has been replaced by --no-redact. This can be paired with --include-placeholders to return a interpolate-able config with all the available secrets from a running OpsMan. This closes issue #356. The OpsMan API changed so that IAAS Configurations were redacted at the API level.

new command diagnostic-report returns the full OpsMan diagnostic report which holds general information about the targeted OpsMan's state. Documentation on the report's payload can be found here.
om interpolate now can take input from stdin. This can be used in conjunction with the new diagnostic-report command to extract a specific section or value from the report, simply by using the pipe operator. For example,
```
om -e env.yml diagnostic-report | om interpolate --path /versions
```
This will return the versions block of the json payload:
```
installation_schema_version: "2.6"
javascript_migrations_version: v1
metadata_version: "2.6"
release_version: 2.6.0-build.77
```
staged-director-config now checks ints and bools when filtering secrets
configure-director and staged-director now support iaas-configurations. This allows OpsManager 2.2+ to have multiple IAASes configured. Please see the API documentation for your version of OpsMan for what IAASes are supported.

If you are using iaas_configuration in your properties-configuration and use iaas-configurations
you'll receive an error message that only one method of configuration can be used.

Provide feedback