Bug #3111
closedv2 API calls to /api/[class]/[object]/parameters/[parameter] don't work correctly
Description
If calling the v2 API with e.g.:
/api/hostgroups/myhostgroup/parameters/myparam
/api/hosts/myhost/parameters/myparam
I get the first parameter named myparam found. It doesn't care if its associated with the host, its hostgroup, etc.
I suggest returning just parameters associated with that object (or smart parameters).
What would be extremely useful for hosts, is a way to return a smart parameter, like if rendering kickstart templates or externalNodes:
/api/hosts/myhost/parameters/myparam would then return the host parameter myparam, if not set the hostgroup parameter myparam, if not set the operating system parameter myparam, if not set the common parameter myparam.
Steps to reproduce:
1. set a common parameter "myparam" value "1"
2. set a hostgroup parameter "myparam" value "2"
3. set a host parameter "myparam" value "3"
The api call for host and hostgroup is going to always return "1" as the parameter has been stored first.
Updated by Joseph Magen about 11 years ago
Updated by Joseph Magen about 11 years ago
- Status changed from New to Ready For Testing
Updated by Dominic Cleal about 11 years ago
- Related to Feature #3220: API for "rendered" view of host parameters, taking into account inheritance added
Updated by Dominic Cleal about 11 years ago
Filed the render type API view as #3220, I think it's a good idea.
Updated by Dominic Cleal about 11 years ago
- Related to Tracker #3112: [TRACKER] Issues to be released in 1.3 RC or final added
Updated by Anonymous about 11 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 9d743410afc311dc96ba6653ae5787181d197dcf.
Updated by Lukas Zapletal about 11 years ago
- Related to deleted (Tracker #3112: [TRACKER] Issues to be released in 1.3 RC or final)