You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When fetching all jobs for a namespace, the stubbed jobs in the response do not include the Namespace. Yes, it could technically be extracted from the URL, but I would expect the response objects to include all identifying properties.
The property is already in the JobListStub struct, but it isn't provided in the Stub method:
Add Namespace as a top-level field in `/v1/jobs` stub.
The `/v1/jobs` endpoint already includes the namespace under `JobSummary`, though the API is odd, as typically the job ID and Namespace are in the same level, and the oddity complicates the UI frontend development.
The downside of adding it is redundant field, that makes the response body a bit bigger, specially for clusters with large jobs. Though, it should compress nicely and I expect the overhead to be small to overall response size. The benefit of a cleaner and more consistent API seem worth it.
Fixes#10431
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
When fetching all jobs for a namespace, the stubbed jobs in the response do not include the Namespace. Yes, it could technically be extracted from the URL, but I would expect the response objects to include all identifying properties.
The property is already in the
JobListStub
struct, but it isn't provided in theStub
method:nomad/nomad/structs/structs.go
Lines 4334 to 4354 in f743780
This was tested on main.
The text was updated successfully, but these errors were encountered: