A cross-platform CLI client for Environment Manager

pip install envmgr-cli

See Configuration for further install instructions.

envmgr is designed to provide an intuitive, human readable interface around the lower level Environment Manager Python Library

All envmgr commands are exposed behind a set of verbs (get a status, schedule some downtime, wait for an ASG, etc). Verbs are always the first value provided to envmgr and there is only ever one verb per command.

The cli interface is described in docopt. The easiest way to discover and understand the different usage patterns available is to simply run

envmgr --help

By default, envmgr commands will output a human friendly response useful for testing single commands at a time. To help scripting or chaining results together, all commands also accept a --json argument which will return the raw JSON response from Environment Manager:

>> envmgr schedule asg my-asg on in prod
Scheduled 1 instance in my-asg to: ON

>> envmgr schedule asg my-asg on in prod --json
{"ChangedInstances": ["i-0afe2276909859130"], "ChangedAutoScalingGroups": ["my-asg"]}

In the examples below, assume that 'prod-1' is an environment, 'AwesomeService' is a service and 'my-asg' is an ASG, all of which are already registered in Environment Manager.

envmgr get AwesomeService health in prod-1

Gets the health status of all instances of AwesomeService, in all slices.

envmgr get AwesomeService active slice in prod-1

Gets the the active slice information for the AwesomeService service in prod-1 environment.

envmgr get asg my-asg status in prod-1

Gets the status of the my-asg ASG in the prod-1 environment. Status is calculated as an aggregate of all instances in the ASG.

envmgr get asg my-asg schedule in prod-1

Gets the schedule value set on the my-asg ASG in the prod-1 environment. Note this will tell you what the schedule is configured to - not the current state according to the schedule.

envmgr get deploy status a2fbb0c0-ed4c-11e6-85b1-2b6d1cb68994

Gets the current status of the deployment with ID a2fbb0c0-ed4c-11e6-85b1-2b6d1cb68994.

envmgr wait-for deploy a2fbb0c0-ed4c-11e6-85b1-2b6d1cb68994

Blocks and waits until the deployment with ID a2fbb0c0-ed4c-11e6-85b1-2b6d1cb68994 either succeeds or fails.

envmgr wait-for asg my-asg in prod-1

Blocks and waits until all instances in the ASG my-asg are ready for deployment (In Service).

envmgr wait-for healthy AwesomeService in prod-1

Blocks and waits until the service AwesomeService is running with all healthchecks passing.

envmgr schedule asg my-asg off in prod-1

Sets the schedule of the ASG my-asg in prod-1 to be off permanently until further notice.

envmgr publish build-22.zip as AwesomeService 1.2.9

Publish the file build-22.zip as version 1.2.9 of AwesomeService.

envmgr deploy AwesomeService 1.2.9 in prod-1

Deploy the published version 1.2.9 of AwesomeService into the prod-1 environment.

envmgr toggle AwesomeService in prod-1

Toggle the upstreams for AwesomeService in the prod-1 environment.

All calls to Environment Manager require authentication, which can be provided in 1 of 2 ways.

Either export your credentials as environment variables:

ENVMGR_USER=myusername
ENVMGR_PASS=mypa$$word

Or provide a --user and --pass value to each commad:

envmgr get MyService health in prod --user="sarah" --pass="pa$$word"

Note: It's recommended to only use this method in CI environments.

The hostname of your Environment Manager instance is configured similarly to your credentials:

Export your hostname as an environment variable:

ENVMGR_HOST=environmentmanager.corp.local

Or provide the hostname with each command:

envmgr get MyService health in prod --host=environmentmanager.acme.com

Install development dependencies:

pip install -e .

Run all tests:

pytest -v