Edit existing Compute Environments
evaluating
T
Tangerine yellow Ladybug
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?
Rob Newman
evaluating
F
Flamingo pink Python
considering the upcoming features to allow for setting Nextflow Config from the CE, it seems like this would be a really important feature to have. It is very common to adjust and update Nextflow Configs over time. I dont want to have to rebuild a new CE every time I need to update the Nextflow Config, and other configs, attached to it.
However one note about the OP;
> 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?
I do not think I would recommend giving each pipeline a separate CE. In general I think it would be better to have fewer CE's, based on what resources are being used.
Rob Newman
acknowledged