Better handling of bootstrap and purge errors
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 522
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 137
Description
### Is your feature request related to a problem? Please describe.
The bootstrap and purge commands currently fail hard on common errors such as:
- realm is already bootstrapped
- realm does not exist or is not bootstrapped
It would be a better UX if we could ignore these errors via a command line option.
Also, the logged messages do not clearly specify which realm failed. In case many realms were provided to the command, that's confusing.
### Describe the solution you'd like
No more annoying messages.
### Describe alternatives you've considered
_No response_
### Additional context
_No response_
Contributor guide
Research direction
Start by locating the bootstrap and purge command entry points and the handling for already-bootstrapped, missing, and unbootstrapped realms. Check how command-line options and per-realm log messages are implemented. Done means an option can ignore these common errors and messages identify the affected realm when multiple realms are supplied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100