3 Commits

Include renames

Author	SHA1	Message	Date
Yan Bondarenko	1b576bc638	fix(registry): drop the backing object's UID from remapped error details ... WrapPreservingStatus rewrites Group, Kind and Name of a backend status to the aggregated resource but left Details.UID as the HelmRelease's, so a client that keys on details saw an identity the tenant cannot look up. The UID goes with the rest of the remap, and a test pins it. Signed-off-by: Yan Bondarenko <202671653+yankawai@users.noreply.github.com> Assisted-by: LLM	2026-09-18 17:30:33 +04:00
Yan Bondarenko	29351bd7fa	fix(registry): report aggregated resource identity in errors ... Backing resource names are not part of the aggregated API contract. Clients need the requested resource identity and the original status code and reason to handle rejected writes consistently. Signed-off-by: Yan Bondarenko <202671653+yankawai@users.noreply.github.com> Assisted-by: LLM	2026-09-18 17:30:33 +04:00
Yan Bondarenko	39da2300d2	fix(registry): keep backend status codes on aggregated write errors ... Aggregated endpoints must retain backend HTTP codes and reasons so clients can distinguish conflicts and admission failures. Dry-run deletion also depends on current finalizers, which a cached read can miss. Signed-off-by: Yan Bondarenko <202671653+yankawai@users.noreply.github.com> Assisted-by: LLM	2026-09-18 17:30:33 +04:00