)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":14394,"name":"Dale Smith","email":"dale@catalystcloud.nz","username":"dalees"},"change_message_id":"458725e99cc65159ff6ddc556c960ddce67c2a3f","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":1,"id":"99651b6f_11f061bb","updated":"2025-09-12 00:44:59.000000000","message":"I see the intent of this, and it\u0027s technically reasonable but I feel like there\u0027s a bigger problem to address with how `admin` interacts with Magnum API, and thus the dashboard.\n\n1. Seeing all clusters in Magnum UI when they actually aren\u0027t part of the current project is misleading and dangerous. We\u0027ve had an admin delete all clusters in a test project (also test region), not realising some were from other projects.\n2. Being able to see a cluster but not modify it isn\u0027t a great experience (and the 404 is confusing - you just saw it!). I think I\u0027d rather *allow* resize/modify than remove it, if it was visible.\n\nLogging in as `admin` to the dashboard should be discouraged and rarely used IMO. But when used, the experience should be similar to other projects (Nova instances, etc).\n\nImplementing `--all-projects` or other convention from other OpenStack service APIs would help with #1, and help with consistency.\n\nThoughts?\n\nWhat is the problem you\u0027re trying to solve, and who does it affect? Customers using OpenStack with `admin` credentials, or only Operators?","commit_id":"4812585772dbaa9bdb5c2aa7df522d615d747b13"}]}