-
-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make spot product description config #214
Merged
cristim
merged 5 commits into
LeanerCloud:master
from
russellballestrini:make-spot-product-description-config
Feb 9, 2018
Merged
Make spot product description config #214
cristim
merged 5 commits into
LeanerCloud:master
from
russellballestrini:make-spot-product-description-config
Feb 9, 2018
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
modified: autospotting.go modified: core/autoscaling.go
cristim
approved these changes
Feb 8, 2018
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, once exposed to Terraform and CloudFormation!
@xlr-8 do you have any comments?
modified: autospotting.go modified: cloudformation/stacks/AutoSpotting/template.json modified: terraform/autospotting.tf modified: terraform/autospotting/lambda.tf modified: terraform/variables.tf
russellballestrini
changed the title
WIP: Make spot product description config
Make spot product description config
Feb 8, 2018
cristim
approved these changes
Feb 9, 2018
12 tasks
cristim
pushed a commit
that referenced
this pull request
Feb 9, 2018
#214 broke terraform deployments due to this missing variable.
I would have simply added a small check as we have the "valid values" in order to ensure it's included, or fallback on the default one. I can open an issue if you think this is relevant |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue Type
Summary
The
Linux/UNIX
product description does not have the price history for the most recent 2 instance type generations, as proved here: http://pad.yohdah.com/598/spot-product-no-historyAs a result we have decided to change the default SpotProductDescription to
Linux/UNIX (Amazon VPC)
as well as make it configurable for backwards compatibility reasons (and so that we can support other operating systems like Windows, etc.)Spot Product Description
fromLinux/UNIX
toLinux/UNIX (Amazon VPC)
-spot_product_description
Code contribution checklist
to it.
Might fix the following: #206 #213
The code is as simple as possible, readable and follows the idiomatic Go
guidelines.
All new functionality is covered by automated test cases so the overall
test coverage doesn't decrease.
No issues are reported when running
make full-test
.This doesn't work on Mac but I'm pretty but I ran
go fmt
andgo test
variables which are also passed as parameters to the
CloudFormation
and
Terraform
stacks defined as infrastructure code.
support per-group overrides using tags.
configurations.
proven to work using log output from various test runs.
appropriate) and formatted consistently to the existing log output.
new configuration options for both stack parameters and tag overrides.
contribution actually resolves it.