-
Notifications
You must be signed in to change notification settings - Fork 294
Node Pool Nested Stack Name #187
Node Pool Nested Stack Name #187
Conversation
Current coverage is 69.11% (diff: 66.66%)@@ master #187 diff @@
==========================================
Files 4 4
Lines 1130 1130
Methods 0 0
Messages 0 0
Branches 0 0
==========================================
Hits 781 781
Misses 261 261
Partials 88 88
|
@@ -693,7 +693,7 @@ type Config struct { | |||
|
|||
// CloudFormation stack name which is unique in an AWS account. | |||
// This is intended to be used to reference stack name from cloud-config as the target of awscli or cfn-bootstrap-tools commands e.g. `cfn-init` and `cfn-signal` | |||
func (c Config) StackName() string { | |||
func (c Cluster) StackName() string { | |||
return c.ClusterName |
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.
nit: Any specific reason to move this method from Config
to Cluster
? (I guess for now there's no specific reason/it doesn't relate to the main purpose of this PR but you just thought it might be better to do so?
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.
Only that StackName was not available in the context of Cluster functions.
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.
Got it! I somehow missed from where the ClusterName
field is coming.
E2E passed. LGTM 👍 |
@mumoshu do we want to also update the name tags of subresources? |
…-names Node Pool Nested Stack Name
Nest node pool stack name by cluster name to avoid conflict when running multiple clusters.
e.g.