Skip to content

Resolve ID-shaped project and environment names after an ID miss - #70

Open
puncsky wants to merge 1 commit into
render-oss:mainfrom
puncsky:fix/resolve-id-shaped-scope-names-20261029
Open

puncsky wants to merge 1 commit into
render-oss:mainfrom
puncsky:fix/resolve-id-shaped-scope-names-20261029

Conversation

@puncsky

@puncsky puncsky commented Oct 30, 2026

Copy link
Copy Markdown

Summary

Recognize a detail lookup's 404 and then try the existing scoped name lookup for ID-shaped project/environment selectors. Real IDs retain precedence; other failures do not trigger fallback.

Motivation

The documented ID-or-name selectors currently classify a valid name by its shape and stop after an ID miss, so some accepted names cannot be selected.

How to verify

go test ./cmd/... ./pkg/... ./internal/...
  • All 57 development packages pass on the candidate.
  • Resolver and real pg/kv list tests cover ID-shaped names, real-ID precedence, ambiguity, missing names, project scoping and fallback only on 404. Transport errors, other HTTP errors and invalid success bodies retain failure behavior.
  • New-code lint is clean against c31e586e; full lint on unmodified main reports 92 pre-existing findings with the pinned golangci-lint v2.14.0.

Release notes

Project and environment selectors resolve ID-shaped names after an ID lookup returns not found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant