Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add StatusCategory reason #1697

Merged
merged 3 commits into from
Nov 8, 2023
Merged

Add StatusCategory reason #1697

merged 3 commits into from
Nov 8, 2023

Conversation

gavinbunney
Copy link
Collaborator

Add a reason field to StatusCategory with default explanations for each ZuulStatusCategory type.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Appreciate reviews on the descriptions here 🤞 determining actual usage & keeping things obvious is sometimes a challenge

@karim-z karim-z self-requested a review November 7, 2023 21:28
SUCCESS_NOT_FOUND(
ZuulStatusCategoryGroup.SUCCESS,
3,
"Successful with no resource found"), // This is set on for all 404 responses
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe something a little more explicit? "Successfully proxied. Origin indicated no resource found"..?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated to: Successfully proxied, origin responded with no resource found

@gavinbunney gavinbunney merged commit b6b0f73 into master Nov 8, 2023
5 checks passed
@gavinbunney gavinbunney deleted the gavin/status-reason branch November 8, 2023 00:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants