Basic DCOS subcommand

1. Make sure you meet requirements for installing packages

2. Clone git repo for the dcos spark cli:

   git clone git@github.com:mesosphere/dcos-spark.git

3. Change directory to the repo directory:

   cd dcos-spark

4. Make sure that you have virtualenv installed. If not type:

   sudo pip install virtualenv

5. Create a virtualenv for the project:

   make env

1. TODO: Talk about how to configure the root dcos cli

2. source the setup file to add the dcos-spark command line interface to your PATH:

   source env/bin/activate

3. Get started by calling the DCOS Spark CLI's help:

   dcos-spark help

When invoking dcos subcommands from the dev env it includes the dcos- as a prefix, however when this is included into DCOS it will be a subcommand of dcos and will be invoked by dcos spark. dcos-spark help translates to dcos spark help when installed into the dcos-cli.

1. Leaving the env

   deactivate

Tox, our test runner, tests against both Python 2.7 and Python 3.4 environments.

If you're using OS X, be sure to use the officially distributed Python 3.4 installer since the Homebrew version is missing a necessary library.

Tox will run unit and integration tests in both Python environments using a temporarily created virtualenv.

You should ensure DCOS_CONFIG is set and that the config file points to the Marathon instance you want to use for integration tests.

There are two ways to run tests, you can either use the virtualenv created by make env above:

make test

Or, assuming you have tox installed (via sudo pip install tox):

tox

1. List all of the supported test environments:

   tox --listenvs

2. Run a specific set of tests:

   tox -e <testenv>