Name searches don't work when there are other parameters in the search route
Search by name works fine when the resource is searchable globally.
hammer architecture info --name i386 # hits /api/architectures?search= ...
The problem occurs when the name must be searched in scope of some other resource, eg. org:
hammer sync_plan info --name test --organization-id ACME_Corporation # hits /api/organizations/ACME_Corporation/sync_plans?search= ...
The search function doesn't have access to the organization id and the api call fails with "missing parameter" exception.
Refs #4311 - single resource command, associated list command
Ther are solving the issues with selecting correct api route when there is more
than one possible.
#2 Updated by Tomáš Strachota over 5 years ago
- Status changed from New to Assigned
- Assignee set to Tomáš Strachota