Open vivuu1989 opened 10 months ago
Hi @vivuu1989 if I'm seeing it correctly, the alertList is an array? But you're just passing a single value in the task (templateParameters: 'alertList: [todeploy: yes]').
While I don't have experience with such a setup, my assumption would be that you need to pass the "full object" - maybe you can try this once?
Note: I'm away for the coming week and will have limited access to a computer, so my responses might be delayed.
Hi @vivuu1989 if I'm seeing it correctly, the alertList is an array? But you're just passing a single value in the task (templateParameters: 'alertList: [todeploy: yes]').
While I don't have experience with such a setup, my assumption would be that you need to pass the "full object" - maybe you can try this once?
Note: I'm away for the coming week and will have limited access to a computer, so my responses might be delayed.
@huserben In my scenario, in pipeline B I need to override this parameter only and rest of the object parameters as same . Because I need just to trigger pipeline B from pipeline A, where the pipeline B has certain conditions based on this parameter to execute, and this need to be override when executing from pipeline A.
Yep, I get that, however, I'm not sure if that's possible (in general as well as with the task itself...). So that's why I wondered whether you could specify the full object to see if it works like that (meaning the problem might be in the overwriting, not somewhere else).
If this works, we could try to dig deeper. However, I'm not sure how an override would work. An option could be to somehow get the "defaults" as part of the task and then only override what's needed and send the full object (but that seems like more work and I will not have the time to focus on this).
If it works in general (meaning it's supported by Azure Pipelines), it would be good to know what we have to send in the request. Perhaps you can try to trigger some runs manually and capture the traffic to see what is sent. It might just be finding the right format to send...
I have Azure Devops pipeline A to tiger another pipeline (pipeline B in the same project). Here pipeline B has some object type parameters as below and
here in each parameter "alertList", I have a flag "todeploy: yes" to decide whether the particular alert need to be triggered in a particular envt, as below and this settings working fine for pipeline B.
But when I used Pipeline A to trigger the pipeline B,
The Pipeline B is not getting executed and error as below
Not Sure, how to pass these parameters both
envt: dr
andalertList
with flag (todeploy: yes) from pipelineA