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

[DOC] Error responses missing in REST API documentation #7791

Open
1 of 4 tasks
imvtsl opened this issue Jul 22, 2024 · 5 comments
Open
1 of 4 tasks

[DOC] Error responses missing in REST API documentation #7791

imvtsl opened this issue Jul 22, 2024 · 5 comments
Assignees
Labels
1 - Backlog - DOC Doc writer assigned to issue responsible for creating PR.

Comments

@imvtsl
Copy link

imvtsl commented Jul 22, 2024

What do you want to do?

  • Request a change to existing documentation
  • Add new documentation
  • Report a technical problem with the documentation
  • Other

APIs in the documentation show response for success scenario. Responses for error scenarios are not added.

Consider this as an example. Response body is missing for error status codes like 4xx, 5xx, etc.

Refer this issue.

@hdhalter
Copy link
Contributor

@imvtsl - Thanks for submitting an issue, @imvtsl! Can you please check the link above (this issue), as I think you may have added the wrong link.

@imvtsl
Copy link
Author

imvtsl commented Jul 22, 2024

Hi @hdhalter
Thank you for pointing out! I corrected the link now.

@Naarcha-AWS
Copy link
Collaborator

@dblock and @imvtsl: Would a page of common response codes be a good solution for this issue?

@hdhalter hdhalter added 1 - Backlog - DOC Doc writer assigned to issue responsible for creating PR. and removed untriaged labels Jul 23, 2024
@imvtsl
Copy link
Author

imvtsl commented Jul 23, 2024

APIs are not consistent with the error responses. For example, delete document API. See this issue for more details.
Therefore, a page of common error responses would not work for all APIs.

@kolchfa-aws
Copy link
Collaborator

Ideally, error messages should be consistent and self-explanatory. If they are, then we'd only need to provide the possible HTTP response codes in the troubleshooting section. We should try to fix this at the product level.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 - Backlog - DOC Doc writer assigned to issue responsible for creating PR.
Projects
None yet
Development

No branches or pull requests

4 participants