We do the same thing as our app admins are not realm admins. We have a service user that everyone has access to. Then we have the builder put their initials after the name, so I can tell who built it as well as the scheduled time, if scheduled. Any time we touch a pipeline, they have to pull a yaml before they start and we upload it into QuickBase, and we retain the last 5 versions, so that if there is an issue we can restore. Tags have also been very helpful as the number of pipelines has exploded over the past few months.
I don't know if support can migrate them for you, but you can always export them, and then go in and change the yaml so that your account slugs and any usertokens are updated to the new user before reuploading them under your service user.
------------------------------
Sean Boat-Moore
Manager SMB Development
Project Management Office and Quality Control
NCR Corporation
sean.boat-moore@ncr.com | ncr.com
------------------------------
Original Message:
Sent: 11-10-2021 13:28
From: Michael Tamoush
Subject: Creating Pipelines with Multiple admin best practice
It seems that if I create a pipeline, as it is my user token, only I can see the pipelines I have created.
What is the best practice when you have multiple QB developers, all wanting to create pipelines? One person creates all...? I want other admin to be able to troubleshoot or update all pipelines. I guess this is not possible.
How do other people handle this?
------------------------------
Michael Tamoush
------------------------------