-
Notifications
You must be signed in to change notification settings - Fork 38
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
allow for import of rds instances and proxies #279
Conversation
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.
Minor comments, rest LGTM
let rds | ||
let proxy | ||
|
||
if (rdsImports != undefined && rdsImports[orm] != undefined) { |
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.
should we also check for VPC here if required?
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 dont have to, if they want a separate vpc for their workloads i think we should allow it, it would just be on them to peer their vpcs.
If we want to just because were saying its the only use case we support today then i guess we could, im torn on if thats a great idea or not though
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.
Ah that's fair, this is fine 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.
especially because in the lambda case it could still connect, its mainly just for the ecs and eks case. So i dont think we want that check
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.
ah nevermind it still wouldnt be able to connect because of the Security Group
proxy: string | ||
} | ||
|
||
export const kloConfig: pulumi.Config = new pulumi.Config('klo') |
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'm surprised this needs the type hint
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.
doesnt need it, i was trying to get some other things working with config and must have just left it
pkg/infra/pulumi_aws/deploylib.ts
Outdated
@@ -62,7 +62,12 @@ export interface TopologyEdgeData { | |||
target: string | |||
} | |||
|
|||
export const kloConfig = new pulumi.Config('klo') | |||
export interface RdsImport { |
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.
This feels like it belongs in rds.ts
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.
yeah it does let me move it
@@ -1003,174 +1008,6 @@ export class CloudCCLib { | |||
) | |||
} | |||
|
|||
public setupRDS(orm: string, args: Partial<aws.rds.InstanceArgs>) { |
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.
IMO it would have been nice to make the changes and the move separately so it was easier to tell what changed
|
• Does any part of it require special attention?
• Does it relate to or fix any issue?
allows for the import of rds and proxy instances
import looks similar to below in pulumi config
modularizing our pulumi code a bit so that we only add our rds instances if necessary.
tested on ts-sequelize
Standard checks