Can we have the feature to do BULK Update of all the Pipelines in our account without providing the complete pipeline yamls
in progress
R
Revolutionary Salamander
As of today, there is not possibility to do Bulk Update of pipelines using API update (As per the harness documentation: https://apidocs.harness.io/tag/Pipeline#operation/updatePipelineV2)
We would like to have the functionality to do bulk updates to all the pipelines in our account without providing the entire yamls of the pipelines (the process to do single pipeline update as per harness documentation). We have some 1000+ pipelines and to update all the pipelines by the creating an automation script using below process is a bit lengthy and tiresome process and also risky:
1.Get list of pipelines
2.Get pipeline yaml using Get API for each pipeline
3.update the yaml with delegate selector
4.Run update API.
So, it would be great if a feature can be provided to update the pipelines by providing the account, org, project and pipeline identifiers and the yaml code that needs to be added/updated for all the pipelines without providing the entire pipelines yamls would be really helpful.
Thanks.!
Log In
This post was marked as
in progress
V
Voluminous Parrotfish
Hey Rohan Gupta, Thank you for adding this feature to your Jira board. We really need this feature as it is limiting us today from testing and rolling out new capabilities (Pipeline restructuring). we have created "delegates" at project level but we are not able to scale it out to different projects n accounts.
Now that we have migrated all domains to NG, we want to really show teams the new capabilities of NG.
Anything you can do to up the priority and get it implemented in Q2 (for sure) that will be greatly appreciated.
R
Revolutionary Salamander
The main reason why we are looking for updating all the pipelines in our account with delegate Selector tag is "if delegate tag is not provided at any level, Harness should use default tag supplied by us (which we are planing to provide at pipeline level). If override happens at any level, it should take precedence over default."
Rohan Gupta
marked this post as
long-term
We are planning to this in an automated way. I have added your request to our internal ticket
R
Revolutionary Salamander
Rohan Gupta Do you mean, there is an existing ticket in place already for the request I have raised and work is already in progress for this?
Rohan Gupta
Revolutionary Salamander: There is an existing feature request, I have just added your feature request to the existing jira. It's not under development yet.
R
Revolutionary Salamander
Hi Rohan Gupta, Is there any ETA on this item? Also, can you provide the ticket number for this issue?
R
Revolutionary Salamander
Rohan Gupta Any ETA on this please?
Rohan Gupta
Revolutionary Salamander this is planned for a our Q2 I cannot give you an eta because we don’t have a conclusion on the solution.
R
Revolutionary Salamander
Rohan Gupta Ok..thank you.!!
V
Vivacious Leopard
Revolutionary Salamander
We are looking for a similar enhancement feature where we could control the build pipelines following mandatory scans before any deployment takes place in prod/non-prod. Is their any way we can introduce our custom template in all the build pipelines across project using an API or OPA policy. This feature would be beneficial to manage bulk updates to pipelines.