cf-mgmt | Go automation for managing orgs

Compiled releases are available on Github. Download the binary for your platform and place it somewhere on your path. Don't forget to chmod +x the file on Linux and macOS.
Navigate into a directory in which will become your git repository for cf-mgmt configuration. By default, cf-mgmt has the enable-delete-orgs option set to false to avoid unintentional deletions. If you'd like to have cf-mgmt handle deletion of orgs as well, please double check the list of protected-orgs and update the enable-delete-orgs flag to true in the orgs.yml of your config repository. You can also modify these settings using the cf-mgmt-config update-orgs command. Check the config docs to understand the configuration files structure. Check the Concourse docs if not familiar with the fly CLI. You now have a Pipeline ready to apply configuration changes to your foundation. Explore the docs to learn the available commands in cf-mgmt-config, try creating new workspace configs, then commit and push the files to you git repository. Your pipeline should kick in and apply the changes.
Initialize git repository by either cloning a remote or using git init This git repository is going to be used as a place to store the config files and will be consumed by a Concourse Pipeline. You should not push your vars.yml file or any other files with secrets to this repo.
Create initial configuration files. You can either setup your configuration by using init command or export-config if you want to start managing a foundation that already have some workspace setup: init command from cf-mgmt-config if you are wanting to start with a blank configuration and add the config using cf-mgmt-config operations export-config command from cf-mgmt if you have an existing foundation you can use this to reverse engineer your configuration.
(optional) Configure LDAP/SAML Options. If your foundation uses LDAP and/or SAML, you will need to configure ldap.yml with the correct values. LDAP only config SAML with LDAP groups SAML only
Generate the concourse pipeline using cf-mgmt-config cf-mgmt-config [OPTIONS] generate-concourse-pipeline [generate-concourse-pipeline-OPTIONS]
Make sure you .gitingore the vars.yml file that is generated: echo vars.yml >> .gitignore
Update your vars.yml file with your config git repo info, domains and the UAA client info you created in the previous section. Use the UAA Client name as user_id
Commit and push your changes to your git repository. After you fly the pipeline in the next step, the pipeline will observe this repository and start a new run everytime you push new configurations to the repository.
fly your pipeline after you have filled in vars.yml
Look for your new Pipeline in your Concourse console. If everything was properly configured all tasks of your pipeline should execute successfully.
Compiled releases are available on Github. Download the binary for your platform and place it somewhere on your path. Don't forget to chmod +x the file on Linux and macOS. Alternatively, you may wish to build from source.
cf-mgmt is written in Go. To build the binary yourself, follow these steps:. To cross compile, set the $GOOS and $GOARCH environment variables. For example: GOOS=linux GOARCH=amd64 go build.
Install Go.
Clone the repo
Build: cd cf-mgmt go build -o cf-mgmt cmd/cf-mgmt/main.go go build -o cf-mgmt-config cmd/cf-mgmt-config/main.go