Project

General

Profile

Actions

Bug #8828

open

Compute resource cannot be found in API by name

Added by Benjamin Roberts over 9 years ago. Updated almost 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
API
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

There appear to be some API calls which have been broken or incorrectly documented in the 1.7 release.

+ /api/v2/compute_resources/:compute_resource_id 
+ used to accept the resource name as a parameter but now only accepts the id.
+ This was not true of the 1.6 release or other api calls/
+ /api/v2/hostgroups/:hostgroup_id
+ Unable to retrieve nested hostgroups by name or title
+ In 1.6 the name of nested hostgroups was accepted as a parameter.

Is this correct behavior?

Actions #1

Updated by Dominic Cleal over 9 years ago

  • Tracker changed from Support to Bug
  • Subject changed from 1.7 API changes to Compute resource cannot be found in API by name
  • Category set to API

Confirmed on the compute resource issue, though I'm surprised that nested host groups were ever working.. I'm not sure if that can be fixed, as using slashes in host group identifiers is likely problematic.

Actions #2

Updated by Benjamin Roberts over 9 years ago

If the names (which don't include slashes) were unique then they could be used for lookup, however I'm not sure if that is desirable or not

Actions #3

Updated by Dominic Cleal over 9 years ago

Yeah, I think that would cause problems for other users, who often have two identically named groups that are children of other groups (e.g. Europe/Web Servers, Americas/Web Servers).

Actions

Also available in: Atom PDF