jippi/hashi-ui

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

Open

#360 建立於 2017年11月6日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)JavaScript (1,235 star) (157 fork)batch import
enhancementhelp wanted

描述

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.

貢獻者指南

技術棧
javascript
領域
backenddevops
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
JavaScriptConsul APINomad API
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
60
研究方向
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.