micado-scale / micado-scale/component_submitter
Store application status after failed deployment
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
## Description
Currently, the errors of a failed app deployment are available at `/status`. The `/list_app` endpoint does not report any information about a failed deployment, but would actually be a logical spot to return more verbose info (failed app name, adaptor status when failed, error messages, etc...) to the user.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the /status and /list_app endpoint entry points and how failed deployment errors are currently retained. Determine where the failed app name, adaptor status, and error messages can be stored and exposed through /list_app. Done means failed deployments return that information from /list_app while existing /status behavior remains available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100