aws / aws/aws-elastic-beanstalk-cli
eb create --min-instances 0 --max-instances 0 not working
- Dominant language
- Python
- Stars
- 181
- Forks
- 88
- PR merge metrics
- No merged PRs in 30d
Description
### Description
Running eb create with the --instance-types parameter does not set the instance type.
### Steps to reproduce
Run
`eb create testenv --elb-type application --min-instances 0 --max-instances 0 --scale 0 --debug`
### Observed result
```
ebcli.objects.exceptions.ServiceError: Configuration validation exception:
Invalid option value: '0.0' (Namespace: 'aws:autoscaling:updatepolicy:rollingupdate', OptionName: 'MinInstancesInService'):
The minimum instances in service for rolling updates (0) should be less than the maximum instance count for the Autoscaling group (0).
```
### Expected result
Should succeed, create a new environment scaled to zero
### Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
OS: Ubuntu 20.04
EBCLI version: EB CLI 3.19.4 (Python 3.8.5)
Region: eu-west-1
Platform: Ruby 2.7 running on 64bit Amazon Linux 2
### Notes
There is no workaround besides creating the environment, then scaling to zero. Ideally there should be a way to control some of specific configuration details during the create that are currently only available through `eb config`.
Contributor guide
Research direction
Start by reproducing the reported command with EB CLI 3.19.4 on the stated Ruby platform, then trace the eb create entry point and the configuration sent for rolling updates. Done means creating an environment with min-instances, max-instances, and scale set to zero succeeds without the validation error and results in an environment scaled to zero.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100