Skip to content

fix(api): return correct status code for services #5564

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

Conversation

megheaiulian
Copy link
Contributor

Services APIs do not return the correct status code.
In some places we force status code 200 or 201 even when there are
errors and we override the 40x status codes.

@megheaiulian megheaiulian changed the base branch from main to next April 7, 2025 14:22
@megheaiulian megheaiulian force-pushed the feat/correct-services-status-code branch 2 times, most recently from 43ec0cd to c41ea9b Compare April 12, 2025 13:55
Services APIs do not return the correct status code.
In some places we force status code 200 or 201 even when there are
errors and we override the 40x status codes.
@megheaiulian megheaiulian force-pushed the feat/correct-services-status-code branch from c41ea9b to de84384 Compare April 13, 2025 13:37
@megheaiulian
Copy link
Contributor Author

@andrasbacsai I know you're probably very busy and sorry about asking about this but can you please take a look at this 🙏 ?
Its (hopefully) the last part that I need to implement a feature in the Coolify terraform provider...

@megheaiulian
Copy link
Contributor Author

megheaiulian commented Apr 23, 2025

Seems to be handled much better in eee57d4

Move the nullable destination_uuid in #5683

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.

1 participant