Volume Size Not Set to a Valid Value

[bheni]

Describe the bug and expected behavior This bug is on dev only atm. When I make the trial instance changes it will make it will occur on prod also.

When you are creating a deployment and change the instance type from anything to the t2.medium the volume type changes correctly. But the new volume type has a minimum size of 50GB and a maximum size of 50GB. The value stays the same as what it was previously and it will be outside the range.

If the min and max size of the volume change and the value is outside the valid range:

• If it is below set the value to the new min
• If it is above set the value to the new max

To Reproduce (please include link if applicable) Steps to reproduce the behavior:

1. Go to https://hosteddoltdb.hosteddev.ld-corp.com/create-deployment
2. Note the volume size is 100 with labels saying it has a Min size of: 100 GB and a Max size of 16000GB
3. Change the instance type from m4.large to t2.medium
4. Note the volume size is still 100, but the min and max have both changed to 50GB and the current value is no longer valid.