You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(event): do not create/update tags during delete (#16)
* process event requestType to not run when delete
* add taints example to documentation
* add examples with multiple tags combination
* add docker tag documentation
Copy file name to clipboardExpand all lines: README.md
+81-10Lines changed: 81 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,18 @@ It's user responsability to specify the cluster the pools and the tags for each
12
12
13
13
## How to use
14
14
15
+
### Push to AWS ECR
16
+
17
+
Our pipelines publish which new release to the docker hub, but in order to call it from a lambda, it needs to be in the AWS account of your private ECR.
18
+
19
+
Example, but you can tag it with the name you want:
20
+
21
+
```bash
22
+
docker pull ydata/aws-asg-tags-lambda:1.0.0
23
+
docker tag ydata/aws-asg-tags-lambda:1.0.0 <your private ECR>/aws-asg-tags-lambda:1.0.0
Both `CommonTags` and `Tags` of each NodePool are optional, but if you don't specify `CommonTags` neither `Tags` for each NodePool, it will not do anything.
108
+
109
+
Check the following examples for other valid combinations
0 commit comments