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
When you use cluster auto scaling, you must specify `capacityProviderStrategy` and not `launchType`. Unfortunately this is not possible to configure when running a one-off task with this action.
This adds a new input `run-task-capacity-provider-strategy` which takes a JSON array of capacity provider strategy items. When this is specified, `run-task-launch-type` will not be applied.
Copy file name to clipboardExpand all lines: action.yml
+4-1Lines changed: 4 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -55,8 +55,11 @@ inputs:
55
55
run-task-assign-public-IP:
56
56
description: "Whether the task's elastic network interface receives a public IP address. The default value is DISABLED but will only be applied if run-task-subnets or run-task-security-groups are also set."
57
57
required: false
58
+
run-task-capacity-provider-strategy:
59
+
description: 'A JSON array of capacity provider strategy items which should applied when running a task outside of a service. Will default to none.'
60
+
required: false
58
61
run-task-launch-type:
59
-
description: "ECS launch type for tasks run outside of a service. Valid values are 'FARGATE' or 'EC2'. Will default to 'FARGATE'."
62
+
description: "ECS launch type for tasks run outside of a service. Valid values are 'FARGATE' or 'EC2'. Will default to 'FARGATE'. Will only be applied if run-task-capacity-provider-strategy is not set."
60
63
required: false
61
64
run-task-started-by:
62
65
description: "A name to use for the startedBy tag when running a task outside of a service. Will default to 'GitHub-Actions'."
0 commit comments