-
Notifications
You must be signed in to change notification settings - Fork 6
Allow imageId and instanceType to be passed into ASG #213
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
Merged
Merged
Changes from 2 commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -11,6 +11,8 @@ import { GuAmiParameter, GuInstanceTypeParameter } from "../core"; | |||||
// https://www.typescriptlang.org/docs/handbook/utility-types.html#omittype-keys | ||||||
export interface GuAutoScalingGroupProps | ||||||
extends Omit<AutoScalingGroupProps, "imageId" | "osType" | "machineImage" | "instanceType" | "userData"> { | ||||||
instanceType?: InstanceType; | ||||||
imageId?: string; | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This would require the prop to be a parameter so we can cater for stacks with multiple ASGs but enforce using parameters for AMIs.
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That's a nice idea 👍 |
||||||
osType?: OperatingSystemType; | ||||||
machineImage?: MachineImage; | ||||||
userData: string; | ||||||
|
@@ -21,27 +23,25 @@ export interface GuAutoScalingGroupProps | |||||
|
||||||
export class GuAutoScalingGroup extends AutoScalingGroup { | ||||||
constructor(scope: GuStack, id: string, props: GuAutoScalingGroupProps) { | ||||||
const imageId = new GuAmiParameter(scope, "AMI", { | ||||||
description: "AMI ID", | ||||||
}); | ||||||
|
||||||
const instanceType = new GuInstanceTypeParameter(scope); | ||||||
|
||||||
// We need to override getImage() so that we can pass in the AMI as a parameter | ||||||
// Otherwise, MachineImage.lookup({ name: 'some str' }) would work as long | ||||||
// as the name is hard-coded | ||||||
function getImage(): MachineImageConfig { | ||||||
return { | ||||||
osType: props.osType ?? OperatingSystemType.LINUX, | ||||||
userData: UserData.custom(props.userData), | ||||||
imageId: imageId.valueAsString, | ||||||
imageId: | ||||||
props.imageId ?? | ||||||
new GuAmiParameter(scope, "AMI", { | ||||||
description: "AMI ID", | ||||||
}).valueAsString, | ||||||
}; | ||||||
} | ||||||
|
||||||
const mergedProps = { | ||||||
...props, | ||||||
machineImage: { getImage: getImage }, | ||||||
instanceType: new InstanceType(instanceType.valueAsString), | ||||||
instanceType: props.instanceType ?? new InstanceType(new GuInstanceTypeParameter(scope).valueAsString), | ||||||
userData: UserData.custom(props.userData), | ||||||
}; | ||||||
|
||||||
|
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.
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.
I believe that Riff-Raff currently relies on AMI being configured as a parameter in order to automatically update the underlying AMI during a deployment. That's a widely used feature in the department (and ideally we want every application to do this due to the security benefits it brings), so I think we might need to discourage passing it as a prop for now.
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.
That's a good point. The reason this was added back as an optional prop was to allow for stacks that have multiple ASGs. Currently, that would fail as we'd try to create the same parameter more than once. This would allow a stack to define multiple parameters and pass them into each ASG as required. If we want to go as far as requiring AMI values to be a parameter, we could change the type of
imageId
toGuAMIParameter
to allow for this overriding but prevent the value being hardcoded in the stack.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.
Hmm, I hadn't thought about that other use-case! Maybe we should still allow this then and use patterns/docs to push 'typical' single-ASG stacks towards using an AMI parameter.
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.
I've added a suggestion below which might be the best of both worlds. Agreed that the standard EC2 pattern should then just create the parameter for you!