jippi/hashi-ui

Option to automatically detect Nomad when connected to a Consul that has Nomad

Open

#360 opened on Nov 6, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (1,235 stars) (157 forks)batch import
enhancementhelp wanted

Description

It would make configuration simpler if it was possible for Hashi-UI to detect a Nomad cluster from the Consul cluster it connects to. That way as configuration you only need to tell it what the connection address is for Consul (http://localhost:8500 will do in most cases) and from there it could automatically detect Nomad, thus removing the need to add configuration for the location of Nomad.

Contributor guide

Tech stack
javascript
Domain
backenddevops
Issue type
feature
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.
half day
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
JavaScriptConsul APINomad API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate the configuration module in hashi ui to understand how Consul connection details are currently used. Look for existing logic that queries Consul for service discovery. Then, extend that logic to automatically detect a Nomad cluster by querying Consul's service catalog for Nomad services or by attempting to reach Nomad's API endpoint. The implementation should fall back gracefully if Nomad is not available.