Protected containers: Fix error message in container overview on protected container

What does this MR do and why?

During the review for the implemnentation of the container deletion protection for GraphQL, it was noticed that the displayed error message was missing when a user attempted to delete a protected container image, see !183545 (comment 2640873119).

The frontend error handling was not correctly processing error arrays that contain string values instead of objects with message properties. This update ensures both string and object error formats are properly displayed to users when container image deletion fails.

Changelog: fixed

🛠️ with ❤️ at Siemens

References

Screenshots or screen recordings

Before After
grafik grafik

How to set up and validate locally

  1. Ensure you have the feature flag :container_registry_protected_containers_delete enabled.
Feature.enabled(:container_registry_protected_containers_delete)
  1. Push a container image to the container registry of your GDK to the project http://gdk.test:3000/flightjs/Flight
  2. Go to http://gdk.test:3000/flightjs/Flight/-/settings/packages_and_registries and create (or alter) a container protection rule to protect the recently pushed container image
  3. Go to http://gdk.test:3000/flightjs/Flight/container_registry and attempt to delete an existing container image that should be protected

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

MR Checklist (@gerardo-navarro)

Related to #406797

Edited by Gerardo Navarro

Merge request reports

Loading