The "initial" bootstrap exit 0 with a warning instead of a raw failure instead of failure if realm already exists
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 522
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 137
Description
### Is your feature request related to a problem? Please describe.
I wanted to script a job in k8s to set up the "admin" realm and credientials and not have to do it manually. However, since it exits 0 on and upgrade, it fails the upgrade...
### Describe the solution you'd like
_No response_
### Describe alternatives you've considered
_No response_
### Additional context
_No response_
Contributor guide
Research direction
Start by tracing the "initial" bootstrap path and its handling when the admin realm already exists; reproduce the behavior from the Kubernetes setup job described in the issue. Done means an existing realm produces a failure and non-zero exit instead of only a warning with exit 0, while the initial setup behavior remains usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kubernetes
- Domain
- backend, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100