Makes spot_fleet_capacity an environment variable so we can have less… #775
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… for dev/staging than prod.
Issue Number
N/A I've just been seeing a lot of compute power getting spun up in staging.
Purpose/Implementation Notes
Staging and dev environments were set to request as much compute power as prod needs. Obviously rather wasteful.
Since the env files are encrypted, this sets
spot_fleet_capacity
to:Types of changes
Functional tests
Testing this in dev would take more time that would be worth it I think. This is a simple change that should be very low risk since I set up the env var in the same way spot_price is set up. Therefore I think we're best off just testing it in staging and iterating from there in the low chance scenario where it fails.
Checklist