Seqera Platform Feature Requests

I would like to be able to edit an existing Compute Environment without the need to Clone and then make Primary again. It seems all options are greyed out once I try to open it to make changes. Resources can be changed on the fly in most cases on AWS. Being our environments are manual, we should be able to edit any piece as it will correspond to edits we have already made in the environment. This is especially important as we head into launching jobs from Seqera Platform. If I have 15 workflows, and I have to edit the CE, I now have to go through all workflows and change the CE. Imagine if we have 50 workflows?

Since AWS only allows 50 CE's per account (which translates to 25 usable CE's for Seqera Platform / Tower), the management of Computer Environments becomes really important. However, the current Compute Environments page is kinda sparse, only listing the Name, Status, Last Active, and ID, of each CE. It would be helpful if more details were viewable from the Compute Environments page, details for each CE such as how many pipelines are using it which pipelines are using it important attributes such as usage of Wave / Fusion, EBS AutoScale, types of EC2 instances, inclusion of GPU Hopefully some sort of compact-view could be developed to show these or other important attributes in the page for each CE. One of the real-world needs for this, is trying to consolidate CE's, to identify which have overlapping settings, and which might not be needed. Right now its pretty difficult to navigate this with the current UI.

When modifying a compute environment, we need to create a new one, migrate the pipelines to it, and delete the old one. However, the compute environment needs to be idle before it can be deleted. Users will often relaunch jobs without updating the compute environment, which can make it tedious to delete a compute environment. Adding an option to Disable a compute environment - in other words, to mark it so no new jobs can be started - would make this much easier. We could then create the new environment, migrate the pipelines, mark the old one as disabled, and just wait a day or two for existing jobs to finish.

Is it possible to have a manual "Check My Connectivity" button in the UI for troubleshooting compute environments (which could just SSH the configured environment to confirm connectivity)?