Standardize exit codes for resources and resource providers
Open
Nobody has claimed this yet.
Issue-Enhancement
- Dominant language
- Rust
- Stars
- 523
- Forks
- 75
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 24
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest version
- Search the existing issues.
Steps to reproduce
There should be different exit codes for different types of errors common across resources and resource providers.
Expected behavior
NA
Actual behavior
NA
Error details
No response
Environment data
NA
Version
v1
Visuals
No response
Contributor guide
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
The issue does not name any files, tests, or entry points. Start by locating how resource and resource-provider failures currently determine process exit status, then document the proposed error categories and codes. Done means the behavior is defined consistently across the relevant resources and providers and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100