Hi, @automating cluster creation Using the CLI for automated cluster setup is a valid approach. @security Storing secure data in git repository is not a good idea. I would assume that you have Cloudbreak deployed and a CI job would have a configured cli to use it. I would also assume that this machine is secured as if you have access to this machine, you basically have access to everything cloudbreak stores. The configuration for CLI is located usually in ~/cb/config, and has the following testenv1: username: user1 password: user1pw server: 10.0.10.12 I'm not sure what kind of CI framework you plan to use (jenkins, teamcity, spinnaker), but basically you could have a CLI installed on an agent or a docker container having the cli and an example configuration file injected from the context of the CI build agent. Another idea is to have the encrypted cli config stored in github, and have the agent the decryption key, and apply the correct config. ... View more