This repository has been archived by the owner on Nov 9, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
19 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
ecs-deploy-action | ||
=== | ||
|
||
What do you mean you don't know what I am? I'm a github action that deploys to your ECS. | ||
|
||
Hmm, let me try and clear this up. If you chuck some yaml in your workflow that looks like this: | ||
|
||
```yaml | ||
- uses: flipgroup/ecs-deploy-action@v1 | ||
with: | ||
cluster: default | ||
service: YourServiceName | ||
image-overrides: YourContainerName=111111111111.dkr.ecr.ap-southeast-2.amazonaws.com/Repo/YourImageName:${{ env.GITHUB_RUN_NUMBER }} | ||
``` | ||
Then I will go and update your service the running containers with a new docker image for you. That easy. | ||
What about environment't variables you ask? I'll just copy it over for you and assume you manage that some other way. | ||
I also play nice with [aws-actions/configure-aws-credentials](https://github.com/aws-actions/configure-aws-credentials) |