Hammer CLI

The requested change would mean backward-incompatible API change, that I don't think we're going to make.

Doesn't hammer host set-parameter and hammer host delete-parameter address your use-case?

Ivan, I don't think {set,delete}-parameter would help here. The issue is hammer clears the parameters when option --parameters isn't used in the update command:

> hammer host update --id 7 --parameters param1=value1,param2=value2
Host updated

> hammer host info --id 7
...
Parameters:
    param1 => value1
    param2 => value2
All parameters:
    param1 => value1
    param2 => value2
    testname => testvalue
    diskinfo2 => test
...

> hammer host update --id 7 
Host updated

> hammer host info --id 7
...
Parameters:               

All parameters:
    testname => testvalue
    diskinfo2 => test
...

From the log:

[ INFO 2017-08-25T13:40:03 API] PUT /api/hosts/7
[DEBUG 2017-08-25T13:40:03 API] Params: {
    "host" => {
                   "compute_attributes" => {
            "volumes_attributes" => {}
        },
             "content_facet_attributes" => {},
        "subscription_facet_attributes" => {},
           "host_parameters_attributes" => [],
                "interfaces_attributes" => []
    }
}

This is a hammer issue. API works fine.

Applied in changeset hammer-cli-foreman|1b8d8237d55661e2c956b3a6052688367bfee559.