Sometimes we must use a connection in a new folder as well. A function to copy a fully configured connection with the secrets to a new folder should be useful.

Comments

  • copy/move shoud be better :D :D

  • To better understand the request, we would like to clarify a few details:

    1. Are you typically copying connections from a folder to the global level, from one folder to another, or from the global level to a folder?
    2. Are you manually creating a single connection or multiple connections from one location to another?
    3. Are you referring to a "copy to" function that would retain the original record, or a "move to" function that would transfer the connection to a new location?
    4. Approximately how many times per week do you perform this action manually?

  • Hi!
    1. typically I copy connections from folder level to another folder.
    2. We copy multiple connections from folder to folder (the scenario is the following; we continously onboard development teams working on the same project, (and we have several big (2-5 years) projects) and these teams use the same integrations in their pipelines, but they need separated folders because that isn't good if they can accidentally use each others templates.
    3. if I should develop a functionality like this, I definitly make both options :D (actually, some days ago - as administrator - I had to move several connections and templates to a new folder, but I didn't knew the password / tokens for all of these connections, so I had to try to contact all of the tech user owners. To move or copy a connection is pain in the ass because it's an admin duty, but we don't have access to the secrets.
    4. I the last weeks I had to copy folder connections more than 20 times, but usually it (create a copy from some connections) happens only once per 1-2 months.