GET /namespaces/ lists every namespace with the number of nodes under it. However, consumers that need to know which namespaces are authoritative (git-backed) vs. ad-hoc (UI-created) have to call this endpoint and then call GET /namespaces/{name}/git for each to read github_repo_path.
This makes answering "what's the universe of git-backed namespaces in this DJ instance?" expensive, which is relevant for skills/CLIs/CI lints that want to enforce "only reference nodes from a namespace owned by source control."
GET /namespaces/lists every namespace with the number of nodes under it. However, consumers that need to know which namespaces are authoritative (git-backed) vs. ad-hoc (UI-created) have to call this endpoint and then callGET /namespaces/{name}/gitfor each to readgithub_repo_path.This makes answering "what's the universe of git-backed namespaces in this DJ instance?" expensive, which is relevant for skills/CLIs/CI lints that want to enforce "only reference nodes from a namespace owned by source control."