Add filtering capability to the HTTP APIs
Open
Nobody has claimed this yet.
stage/needs-discussion
theme/api
type/enhancement
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
Nomad version
0.5.0
Issue
The issue is basically summed up here (https://groups.google.com/d/msg/nomad-tool/4gXi9Eakb8Y/tFY3c8ktBwAJ). Not sure whether the author ever logged an issue?
It would be very useful to add filtering parameters to all GET resources on the HTTP APIs.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked Google Groups discussion and locating Nomad's HTTP API handlers for GET resources. Define the filtering parameters and scope before changing code; done would require consistent filtering across all intended GET resources, with corresponding tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100