hashi-ui should (optionally) indefinitely retry connections to nomad instead of failing to start.
Contributor guide
Tech stack
javascriptrest api
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Examine the main entry point of hashi ui, likely index.js or app.js, to understand how connections to Nomad are established. The current implementation fails on startup if Nomad is unreachable. Add an optional retry mechanism with exponential backoff and a configuration flag. Review similar issues or PRs in the repository for retry patterns.
