This repository has been archived by the owner on Dec 21, 2023. It is now read-only.
API: Get Event returns HTTP 500 when event cant be found. Should be 404 #1655
Labels
area:api
good first issue
Issues for getting started developing Keptn
type:bug
Something is not working as intended/documented
type:chore
Provides value to the (dev) team
Projects
Milestone
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I will take this |
johannes-b
added
type:bug
Something is not working as intended/documented
next-sprint
Items that should be discussed and implemented in the next sprint
labels
Aug 3, 2020
The /GET event endpoint still returns a 500 - Internal Server error, because the GetEvent function returns an error which leads to the 500 error. Task:
Definition of Done:
|
johannes-b
removed
the
next-sprint
Items that should be discussed and implemented in the next sprint
label
Aug 7, 2020
bacherfl
added a commit
that referenced
this issue
Aug 10, 2020
bacherfl
added a commit
that referenced
this issue
Aug 10, 2020
bacherfl
added a commit
that referenced
this issue
Aug 10, 2020
bacherfl
added a commit
that referenced
this issue
Aug 11, 2020
johannes-b
moved this from Ready for review
to Done/presented in community review (column will be cleaned regularly)
in Working items
Aug 13, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area:api
good first issue
Issues for getting started developing Keptn
type:bug
Something is not working as intended/documented
type:chore
Provides value to the (dev) team
When waiting for an evaluation-done event a client has to call GET /event with the keptnContext and evaluation-done as event type. When the event does not yet exists the Keptn API returns an HTTP 500 (Internal Server Error) instead of something that is more descriptive, e.g: 404 Resource Not Found.
HTTP 500 is definitely misleading as this is not an internal server error. It is really about an event not being present - so - a more suitable HTTP Status Code should be used, e.g: 404
The text was updated successfully, but these errors were encountered: