Pipeline names are unique to an organization, but not a workspace.
complete
C
Coral reef Lamprey
We just added a new workspace and discovered that pipeline names must be unique within an organization, instead of at the workspace level.
Among other things, this now means we have a pipeline called "BLAST" and one called "BLAST_Search", but I'm really not sure what we're going to do if we wind up with a third workspace.
Mattia
We recently released an update on Seqera Platform Cloud that enforces pipeline name uniqueness at the workspace level but not at the organizational level. This allows pipelines to have the same name in different workspaces of the same organization. The feature will be available as well in the next enterprise release 24.2.x
M
Mighty Bird
Mattia Fantastic! That will be very useful!
This post was marked as
complete
C
Continuous Squid
It would be nice to have the name unique in workspace: for security reason we are creating a workspace for each group and project in our institute. This means that we may need to install the same pipelines in > 10 workspaces, and need to give it always a different name, which ended as "workspace-pipelinename".
Rob Newman
evaluating
Change to new status
Rob Newman
under review
Rob Newman
acknowledged