-
Notifications
You must be signed in to change notification settings - Fork 314
Restore default values in cfn template for ComputeInstanceType #2284
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
Restore default values in cfn template for ComputeInstanceType #2284
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #2284 +/- ##
========================================
Coverage 62.12% 62.12%
========================================
Files 40 40
Lines 6149 6149
========================================
Hits 3820 3820
Misses 2329 2329 Continue to review full report at Codecov.
|
| "MasterInstanceType": { | ||
| "Description": "Head node EC2 instance type", | ||
| "Type": "String", | ||
| "Default": "t2.micro", |
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.
let's remove the default for the head node.
| "ComputeInstanceType": { | ||
| "Description": "ComputeFleet EC2 instance type", | ||
| "Type": "String", | ||
| "Default": "t2.micro", |
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.
We can improve the description by highlighting the fact that this parameter is useless for Slurm but needed as CFN param.
We can use NONE instead of t2.micro to avoid hiding other errors. In this way we'll be sure that a value is always passed.
Compute instance type parameter is not rendered if scheduler is Slurm. This caused the error `Parameters: [ComputeInstanceType] must have values` in CloudFormation because a value was still expected. With this commit we set "NONE" as default to prevent this value being silently used as if set by the user. Signed-off-by: ddeidda <ddeidda@amazon.com>
c5434e1 to
fda018e
Compare
) Compute instance type parameter is not rendered if scheduler is Slurm. This caused the error `Parameters: [ComputeInstanceType] must have values` in CloudFormation because a value was still expected. With this commit we set "NONE" as default to prevent this value being silently used as if set by the user. Signed-off-by: ddeidda <ddeidda@amazon.com>
) Compute instance type parameter is not rendered if scheduler is Slurm. This caused the error `Parameters: [ComputeInstanceType] must have values` in CloudFormation because a value was still expected. With this commit we set "NONE" as default to prevent this value being silently used as if set by the user. Signed-off-by: ddeidda <ddeidda@amazon.com>
Compute instance type parameter is not rendered if scheduler is Slurm. This caused the error
Parameters: [ComputeInstanceType] must have valuesin CloudFormation because a value was still expected.With this commit we set "NONE" as default to prevent this value being silently used as if set by the user.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.