Zack Patrick

Instead of going over each request/client option, I should have a slimmed down version in the readme and examples of each option in godoc, e.g.: ``` # Request Options *...

Right now, you need to totally override the request reader if you want to read custom error types. It should be more simple to try and marshal into errors. Perhaps...

CLI: Allow users to easily switch between Layer0 instances with a `-i/--instance` flag

1

We should store the `endpoint` and `token` variables for each user's Layer0 instance in a flat file (perhaps `~/.layer0/config.ini`?) that can be referenced - ala the aws cli. We would...

Set LaunchType when creating Services and Tasks

3

# Summary Enable Layer0 to deploy services and tasks using AWS Fargate. # Implementation ## Retract Typed Environments Decision It turns out that tying EC2/Fargate compatibility to environments is unnecessary...

Merge api-refactor branch into develop

1

Once https://github.com/quintilesims/layer0/issues/500 has been finished, we need to merge api-refactor into develop so we can get back into a sane branching workflow. This work item will be considered "done" once...

Update aws-sdk-go pkg

1

Some of our users have a need for some of the new task definition parameters provided by ECS, specifically, the `LinuxParameters` field. To get this out to our users as...

Create scheduled tasks

1

http://docs.aws.amazon.com/AmazonECS/latest/developerguide/scheduled_tasks.html

Refactor entity IDs and prefixes

2

We could change the `client` and `api` package to always communicate with fully-qualified entity ids. This could help simplify the `provider/aws` package tremendously. If we wanted, users could still only...

Show dependency tree on CLI

2

Similar to the `tree` command in bash, implement a similar command in the Layer0 CLI to show the relationship between entities.

Merge `l0-setup` into the `l0` binary as a top-level command, e.g. `l0 setup init`