More fine-grained control of Pipeline visibility to specific users
acknowledged
W
Weekly Elk
Is it possible to get fine-grained control over what Pipelines a given user can see? I know this would be possible by splitting up the Pipelines into different Workspaces, but these Pipelines share all their infrastructure (Compute Environments, Credentials, Secrets), so it would be frustrating to recreate them across separate Workspaces. Is it possible to achieve this through shared Workspaces?
Note: we have other Workspaces that do not share the same infrastructure as this one, so we would not want those to also get any shared infrastructure.
Drew DiPalma
Merged in a post:
Selectively hide pipelines across shared workspaces
G
Gold Orca
Shared workspace pipelines are currently all-or-nothing at the organization level. The platform does not allow for selective sharing.
We have ten workspaces and we would like to share a pipeline across nine of the workspaces but not the other one.
Ideally we would have one admin workspace where all shared pipelines could be published, then the admin user could decide which workspaces (based on certain user groups) have access to which shared pipelines. Today we have to publish the pipeline to several different workspaces independently and manually manage updates.
Rob Newman
acknowledged