0.10.0

New in this release:

• stage-product will now inform you if a product has already been staged.
• Full support for product configuration.
• om curl now "pretty prints" the JSON returned in responses.
• om <command> --help will now print command-specific help.
• Addresses some more issues with network connection timeouts.
• Fixes a regression in the apply-changes command that would prevent users from authenticating correctly when invoking the command.

om configure-product

This command can be invoked as follows:

$ om --target https://opsman.example.com \
     --username "some-username" \
     --password "some-password" \
     configure-product \
       --product-name "my-product" \
       --product-properties '{
         ".my_job.my_property": {
           "value": "some-property"
         }
       }' \
       --product-network '{
         "network": { "name": "my-subnet" },
         "other_availability_zones": [
           { "name": "us-central1-a" },
           { "name": "us-central1-b" },
           { "name": "us-central1-c" }
         ],
         "singleton_availability_zone": { "name": "us-central1-a" }
       }' \
       --product-resources '{
         "consul_server": {
           "instance_type": {"id": "automatic"},
           "instances": 3,
           "internet_connected": true,
           "persistent_disk": {"size_mb": "automatic"}
         },
         "diego_brain": {
           "elb_names": ["tcp:banana-cf-ssh"],
           "instance_type": {"id": "automatic"},
           "instances": 1,
           "internet_connected": true,
           "persistent_disk": {"size_mb": "automatic"}
         }
       }'

The properties, network, and resources JSON fields follow the structure of those same fields as described in the OpsManager API. Look to the API docs for more information about how to structure your specific configuration.