Jcf

If you use CloudFoundry you'll know that some commands/queries require you to use cf curl and that can get a little tedious. This gem is a wrapper around cf curl to make it easier to query the CloudFoundry API, as well as being able to query the CloudWatch metrics for the AWS services that are used by the CF services.

Some handy features:

jcf u jamie # find all users with a partial username of jamie
jcf o foo  # find all orgs with a partial name of foo
jcf sb s3 # find all service brokers with a partial name of s3
jcf so bucket # find all service offerings with a partial name of bucket
jcf sp medium # find all service plans with a partial name of medium

# find all metrics for the rds-broker service, postgres offering, output it to a csv file
jcf m postgres -t 'rdsbroker-{guid}' -o admin -f csv --ouput postgres-metrics.csv

gem install jcf

A convenience rake task has been included to do this locally:

rake install

Or you can just build it instead:

rake build

Make sure you're logged into the CloudFoundry you want to query. You can then run the jcf command to see the available commands:

$ jcf
Commands:
  jcf metrics ENV TYPE
  jcf organizations [NAME]
  jcf service_brokers [NAME]
  jcf service_instances [NAME]
  jcf service_offerings [NAME]
  jcf service_plans [NAME]
  jcf spaces [NAME]
  jcf users [NAME]
  jcf version                                 # Print JCF app version

Each command has a --help option to show the available options. They also have aliases for the short and long form of the command. For example:

jcf organizations
jcf orgs
jcf o

jcf service_brokers
jcf sb

Ignoring metrics, all other types can list all or filter based on a given name.

jcf organizations

jcf organizations my-org

Metrics queries AWS for backend CloudWatch metrics. It will output a table of the metrics for each service instance.

Because CF doesn't give access to the underlying AWS details for us to query, we have to make some assumptions:

• You need to be logged into the AWS account that the CF is using
• The AWS account has the correct permissions to query the metrics

We need a template for the instance names on AWS. This is a regex that will be used to match the instance names. For example, the rds-broker service has instances with names like rdsbroker-GUID1, rdsbroker-GUID2, etc. The template for this would be rdsbroker-{guid}.

Examples for the template, note that guid is a special value that is filled automatically with the instance guid from CF:

• rdsbroker-{guid}
• s3broker-{guid}
• s3broker-{guid}-bucket-{name}

When you supply a template token that is not guid, you need to supply a --values flag to fill in the value. For example:

jcf metrics OFFERING \
  --org=my-org \
  --template='rdsbroker-{guid}-{name}' \
  --values='name=foobar'

jcf will use the template to determine the AWS guid to query for metrics.

The default format is a table. You can also format as JSON or CSV. For example:

# as json
jcf organizations --format json

# as csv
jcf organizations --format csv

When querying metrics, you probably want the output to a file. You can use the --output flag for this. Progress will be output to STDERR. For example:

jcf metrics production rds-broker \
  --org=my-org \
  --format csv \
  --output rds-broker-metrics.json

After checking out the repo, run bin/setup to install dependencies. Then, run rake spec to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and the created tag, and push the .gem file to rubygems.org.

Bug reports and pull requests are welcome on GitHub at https://github.com/fearoffish/jcf. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the code of conduct.

The gem is available as open source under the terms of the MIT License.

Everyone interacting in the Jcf project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.

• Hanami for the CLI framework I borrowed some ideas from there. Thanks!