Hey all. I've got gocd working generally fine, on kubernetes (GKE) via the helm chart but I'm blundering around a bit on getting materials to use credentials to clone private git repos.
Specifically, what is the actual "best" practice as where to put credentials, particularly if we're defining the pipelines in a yaml/json config repo? Env vars? Parameters? How do I communicate them to the material? I am *really* not a fan of putting credentials in the YAML itself (even if encrypted) as that binds changes to credentials to the source repo, and makes it much harder to automate/orchestrate credential changes. Normally, I'd expect to be able to set username/token as env vars, then reference them in the config but so far that doesn't seem to be working. I can dig into details if needed but more generally: If one is using YAML based pipeline configs, where are you putting credentials, and how do you reference them in the YAML? Thanks! -Mike -- 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/eabe48e7-2f87-4f3a-b220-88f96cc524can%40googlegroups.com.
