Skip to content

Conversation

@hc-github-team-nomad-core
Copy link
Contributor

Backport

This PR is auto-generated from #25716 to be assessed for backporting due to the inclusion of the label backport/1.10.x.

The below text is copied from the body of the original PR.


Fixes #25672 - tl;dr NOMAD_REGION and NOMAD_NAMESPACE are ignored by nomad operator debug

I thought about having Meta.clientConfig() write Meta.region and Meta.namespace, but that felt off, so I opted for a couple of getters that can hopefully be easily discovered if needed for other cases.

Before:

$ NOMAD_REGION=global NOMAD_NAMESPACE=default nomad operator debug
Starting debugger...

Nomad CLI Version: Nomad v1.10.0
BuildDate 2025-04-09T16:40:54Z
Revision e26a2bd2acac2dcdcb623f4d293bac096beef478
           Region:
        Namespace:
          Servers: (1/1) ... etc etc ...

After:

$ NOMAD_REGION=global NOMAD_NAMESPACE=default nomad operator debug
Starting debugger...

Nomad CLI Version: Nomad v1.10.1-dev
BuildDate 2025-04-21T18:49:12Z
Revision c86d63da13145326ae69649fa9c51601dc16914a+CHANGES
           Region: global
        Namespace: default
          Servers: (1/1) ... etc etc ...

Overview of commits

@gulducat gulducat merged commit 42fd27e into release/1.10.x Apr 21, 2025
31 checks passed
@gulducat gulducat deleted the backport/NET-12503-operator-debug-env-region-ns/clearly-eminent-ray branch April 21, 2025 21:46
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 20, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants