hashicorp / hashicorp/nomad

[question] Is there a reason not to have Region in the /v1/node/{NodeID} API call

Open
#9,409 4 comments 0 reactions 0 assignees View on GitHub
theme/api type/enhancement
Dominant language
Go
Stars
17k
Forks
2.1k
Avg merge
1d 9h
Merged PRs (30d)
105

Description

When making an API call {ServerNodeIP}:4646/v1/node/{NodeID} I can see Datacenter but not Region.

In the example of using the same Datacenter name used in different Region(s), the node API call does not clearly define the Node's position in a hierarchy

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the /v1/node/{NodeID} API endpoint and its current response fields, especially Datacenter. Check how Region is represented elsewhere in the node or API models, then determine the expected response shape and compatibility requirements. Done means the node response clearly identifies a node's region when datacenter names overlap.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.