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
Copy file name to clipboardExpand all lines: README.md
+19Lines changed: 19 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -366,6 +366,25 @@ To tag your tasks:
366
366
wait-for-task-stopped: true
367
367
```
368
368
369
+
370
+
## Preserving Empty Values with keep-null-value-keys
371
+
372
+
By default, this action removes empty string, array, and object values from the ECS task definition before registering it. If you want to preserve empty values for specific keys, use the `keep-null-value-keys` input. This is a comma-separated list of key names. When specified, any empty value for those keys will be kept in the registered task definition.
This is useful for cases where a default value is non-null and you want to override the value and set it to null.
387
+
369
388
## Troubleshooting
370
389
371
390
This action emits debug logs to help troubleshoot deployment failures. To see the debug logs, create a secret named `ACTIONS_STEP_DEBUG` with value `true` in your repository.
Copy file name to clipboardExpand all lines: action.yml
+3Lines changed: 3 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -88,6 +88,9 @@ inputs:
88
88
propagate-tags:
89
89
description: "Determines to propagate the tags from the 'SERVICE' to the task."
90
90
required: false
91
+
keep-null-value-keys:
92
+
description: 'A comma-separated list of keys whose empty values (empty string, array, or object) should be preserved in the task definition. By default, empty values are removed.'
93
+
required: false
91
94
outputs:
92
95
task-definition-arn:
93
96
description: 'The ARN of the registered ECS task definition.'
0 commit comments