Skip to content

API: return 404 on resource of non-existing items #2994

Open
@hsmade

Description

When I, for example, request /v1/job/doesntexist/deployment I would expect to get a 404, just like I'm getting on /v1/job/doesntexist.

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    • Status

      Needs Roadmapping

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions