Skip to main content
← Back to list
01Issue
FeatureOpenExtensions
AssigneesNone

#400 Improve idempotency match field heuristic for auto-generated name resources (tagKeys, tagValues)

Opened by stack72 · 5/21/2026

The idempotent create fallback (added in #399) uses matchField to find an existing resource via list when a 409/already-exists error occurs. For resources like tagKeys and tagValues where name is server-generated (e.g. tagKeys/12345), the current heuristic falls back to matchField: name which produces an empty or wrong matchValue. The list scan iterates up to 100 pages and never matches, then throws a generic error.

For tagKeys, shortName exists in insertProperties and is the user-facing unique identifier within a parent. Similar per-resource fields may exist for tagValues and other resources.

The generator should use a smarter heuristic: prefer shortName when displayName is not available and the naming field is auto-generated, or skip emitting idempotency config entirely when no useful match field can be determined.

Discovered during code review of PR #150.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED

Open

5/21/2026, 10:53:07 AM

No activity in this phase yet.

03Sludge Pulse

Sign in to post a ripple.