Traveling Cloud Foundry Admin CLIs
This project packages the CLIs used by Cloud Foundry administrators - the
cf CLI and useful admin plugins, and the
uaac CLI (a Ruby gem). They can be downloaded and used by anyone without requiring Ruby and native extensions.
Support for including useful admin plugins requires:
And some people to start writing admin plugins... hint hint.
See below for the one-line installation instructions.
The goal of traveling-cf-admin is to have very few dependencies.
curl is the only dependency for the simple installation process.
sudo apt-get update sudo apt-get install curl -y
For OS X:
brew install curl
One user - simple installation
From any OS X or Linux terminal run the following command. It will download, unpack, and setup your
curl -s https://raw.githubusercontent.com/cloudfoundry-community/traveling-cf-admin/master/scripts/installer | bash
All users - simple installation
From any OS X or Linux terminal run the following command. It will globally download, unpack, and setup your
curl -s https://raw.githubusercontent.com/cloudfoundry-community/traveling-cf-admin/master/scripts/installer | sudo bash
Alternately see step-by-step instructions below.
To download the latest release https://github.com/cloudfoundry-community/traveling-cf-admin/releases
rm -rf tar xfz cf-admin*.tar.gz wget https://github.com/cloudfoundry-community/traveling-cf-admin/releases/download/v22.214.171.124/cf-admin-126.96.36.199-linux-x86_64.tar.gz tar xfz cf-admin*.tar.gz rm cf-admin*.tar.gz
Rewrite the internal shebangs of ruby-installed binaries:
To check that
uaac are runnable:
You could now create a symlink:
rm -f cf-admin ln -s $PWD/$(ls -d cf-admin* | head -n1) cf-admin
Check that its runnable via the symlink:
To check that the CLIs are runnable:
Finally, add the
cf-admin path into your
This project uses http://phusion.github.io/traveling-ruby/
Create & publish releases
Anyone in the @cloudfoundry-community can be responsible for create new releases whenever new CF CLI or UAAC versions are released. This section contains the instructions.
You are required to use Ruby 2.1 to create releases as this is what traveling-ruby uses.
You will also need to install https://github.com/aktau/github-release to share the releases on Github.
The release version number is directly taken from the CF CLI to be packaged.
To upgrade the uaac version (via
To create the new release, create new commit & git tag, and upload the packages:
This will create three packages:
$ ls cf-admin* cf-admin-188.8.131.52-linux-x86.tar.gz cf-admin-184.108.40.206-linux-x86_64.tar.gz cf-admin-220.127.116.11-osx.tar.gz
It will then create a GitHub release and upload these assets to the release.
scripts/installer with the new CF CLI version.
Release via Concourse
The pipeline status is viewable at http://ci.starkandwayne.com:8080/pipelines/traveling-cf-admin
To setup a pipeline for your own fork (heck why not - perhaps include some additional binaries for your users)
git-repository: email@example.com:<your-org>/traveling-cf-admin.git git-branch: master github-org: <your-org> github-repository: traveling-cf-admin github-private-key: | -----BEGIN RSA PRIVATE KEY----- MIIEpAIBAAKCAQEAum1nnKm7vBDf83l0aDSpZ94nKz9FzEVb5nFTlNEa0w+D0/hb WJ/dxCz20Quzsqq7jiNbVsx19CjoNNZJwcXgE00hIe5tIcxyEdj1ShfzeXD2smOP ... DDRsY7ljzku3Ry9M7Iqn7aV7HaD+SY71RhBwAvzPmNhaLm31KbEM5Q== -----END RSA PRIVATE KEY----- github-access-token: <your-token>
To create & upload the pipeline to your target Concourse:
fly -t snw configure traveling-cf-admin -c ci/pipeline.yml --vars-from credentials.yml