Skip to content

Commit 48637fd

Browse files
committed
docs: modify readme
1 parent 35bd757 commit 48637fd

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

README.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,18 @@ If you do not wish to store your task definition as a file in your git repositor
5656
aws ecs describe-task-definition --task-definition my-task-definition-family --query taskDefinition > task-definition.json
5757
```
5858

59+
If you don't want to create new revisions of your task definition, you can define the task definition family and revision as inputs for the action. By default, the action will use the latest revision of the task definition family if the revision is not specified.
60+
61+
```yaml
62+
- name: Deploy to Amazon ECS
63+
uses: aws-actions/amazon-ecs-deploy-task-definition@v1
64+
with:
65+
task-definition: my-task-definition-family
66+
service: my-service
67+
cluster: my-cluster
68+
wait-for-service-stability: true
69+
```
70+
5971
### Task definition container image values
6072

6173
It is highly recommended that each time your GitHub Actions workflow runs and builds a new container image for deployment, a new container image ID is generated. For example, use the commit ID as the new image's tag, instead of updating the 'latest' tag with the new image. Using a unique container image ID for each deployment allows rolling back to a previous container image.

0 commit comments

Comments
 (0)