MCM-27 — Suggest Missing Tag Values from Resource Topology

← Back to Custom Tag Improvements overview

As a Platform User,
I want MCM to suggest a tag value for a resource that's missing one, based on what its associated resources in the topology already carry,
so that I can fill tagging gaps quickly and consistently instead of guessing the right value myself.

Assumption: this story depends entirely on MCM-26 existing first — there is no topology data to suggest from until that story is built. Also assumed: a suggestion is only made when associated resources agree on a single value for the tag key; if they disagree, no suggestion is offered rather than guessing which one is "right" — confirm this is the intended behavior for conflicting values.

Acceptance Criteria

• When a resource is missing a value for a given tag key, and its associated resources (per MCM-26's topology) share a single common value for that key, the resource's view surfaces that value as a suggestion.
• Accepting a suggestion applies it via the existing tag-update path (see MCM-22), subject to the same allowed-list rules as any other tag update.
• If associated resources carry conflicting values for the tag key, no suggestion is shown (see Assumption above) rather than picking one arbitrarily.
• If associated resources also lack the tag entirely, no suggestion is shown — there's nothing to propagate.

---

Technical Design

This has a hard dependency on MCM-26 — the topology capability proposed there is what this story queries to find "associated resources," and it adds no new relationship data of its own. A new suggestion capability, alongside the topology work from MCM-26, takes a resource and a tag key, looks at its associated resources' tag values, and returns a single suggested value only when they agree; accepting a suggestion reuses the existing tag-update path from MCM-22 rather than a new mechanism. The suggestion surfaces wherever tags are edited for a resource, e.g. the resource detail tags view extended in MCM-25.

---

UI / Frontend Changes

• Resource detail tags view (extended in Add, Update, and Delete Tags from the Resource Detail View) gains a suggestion affordance next to a tag key that's missing a value, showing the proposed value with Accept/Dismiss actions.
• Accepting a suggestion reuses the existing single-resource tag-update save flow and its loading/error states — no separate save mechanism.
• No suggestion UI is shown at all when associated resources disagree or none carry the tag — the tab looks identical to today in that case, not a broken or empty suggestion widget.
• Dismissing a suggestion simply hides it for that session/view; it does not alter the tag or allowed list.