Not sure of your workflow, but in my previous setups this type of initial
configuration involved bootstrapping via curls to API from source
controlled, termplated config a few things such as cluster/elastic
profiles, authorization config, secrets config etc.
This is essentially similar to what the
Hi Chad, Aravind,
Thank you for the feedback.
The primary context of this question is creating our own internal
documentation for how to configure GoCD authentication and authorization.
Since this (theoretically) only needs to be done once on initial setup,
it's probably not worth the headache
