Hello Helge, On Thu, Jun 11, 2020 at 03:00:28 -0700, Helge Walter wrote: > Thank you for your advice. > I think the groovy config-repo plugin is worth a look. There it would be > possible to read such parameters programmatically, e.g. from a file.
As Ketan mentioned, please think about the security implications of it. If you're using it publicly, you need to be careful since it can be powerful and (so) dangerous. > Another idea is some kind of instance specific parameters as used in > pipelines but defined on GoCD instance level -- maybe provided by some kind > of parameter plugin like secret plugins. > I reviewed the secrets management page and found it very useful. So would it > be possible to abuse the secrets plugin to provide the branch for the > materials and configuration repositories? Can all configuration values use > the secrets from secret manager plugins? I thought about that. However, based on the documentation, the only places secrets can be used are the password field of a material and environment variables (and so, within a task in a job as well). So, it doesn't seem like you can use it arbitrarily, which should mean that you can't use it to provide the branch, unfortunately. Another piece of work that is going on now which might be relevant to you: https://github.com/gocd/gocd/issues/6123 It implements some form of templating which might be useful to you. It's a work in progress though and you'll need to wait. 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/20200611103227.eorl2225eoxdglhp%40arvindsv.com.
