layer0
layer0 copied to clipboard
Build, Manage, and Deploy Your Applications
**What does this pull request do?** Fixes #652 **How should this be tested?** Build `l0-setup` and run the following against the preprod AWS account: ``` ./l0-setup init --docker-path=/path/to/my/docker_config uswest2dev ./l0-setup...
### Expected behavior User can create a new l0 instance in us-east-2. ### Actual behavior It fails, since it's not in the list of regions. ### Steps to reproduce the...
**What does this pull request do?** Adds `us-east-2` region to list of valid regions. **How should this be tested?** Deploy L0 to `us-east-2`. **Checklist** - [x] Unit tests - [...
We've observed services flapping with L0 v0.11.0 - it seems that sometimes a service is brought up in a subnet that isn't part of the load balancer's subnets, which causes...
l0-setup is currently broken for new installs due to incompatible params with the AWS 2.0 provider. We should either update the resource and module params to the latest standards, or...
# Troublesome Behavior If a user happens to be managing Layer0 instances across different AWS accounts with different credentials, `l0-setup list` will always return an `AccessDenied` error. Given AWS accounts...
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...
For users who manage Layer0 instances across multiple AWS accounts, it can get confusing to remember which set of AWS credentials pair with which Layer0 instance. This confusion could readily...
We currently have [good developer docs](https://github.com/quintilesims/layer0/blob/develop/DEVELOP.md#test-your-changes) that outline how to update the API and runners for a given deployed Layer0 instance, but we should expand this section to provide more...
### Expected behavior ELB is generally configured with 3 subnets in 3 AZs ### Actual behavior Only a single subnet in a single AZ was configured Events as seen from...