Hello Brendon, On Wed, Nov 21, 2018 at 05:08:43 -0800, [email protected] wrote: > Because I have a need to use shared variables in my pipelines, between > materials and tasks, I am using parameters mainly (as opposed to > environment_variables). However, we would like to schedule pipelines using > parameter overrides. This is not supported currently, only > environment_variables overrides is supported. Why is this the case?
Parameters are in-lined (in memory) as soon as the configuration is saved. They're not available at runtime. This is done as a part of merging templates into pipeline configs. Similarly, templates are also not available at runtime. That's why overriding parameters is not supported. I realize that it can be troublesome because parameters can be used in more places than environment variables can be (in materials, as you said). I think it's an unfortunate decision made a long time ago, to separate the concepts - and in hindsight, is unnecessary. Environment variables could have been a special case of parameters and parameters could have been exposed at the top-level - but it's the other way round. Cheers, Aravind -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
