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.