narocorporation/Naro Deploy
Deploys to ECS in the Naro way
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| aws_role | ARN of the role to (attempt to) assume when performing actions on AWS | yes | — |
| aws_region | AWS region to operate in, e.g. `us-east-1` | yes | — |
| task_definition_family | ECS Task Definition family to update, e.g. `bff` | yes | — |
| ecr_repository | Name of the ECR repository to push images to, e.g. `bff-50e8673` | yes | — |
| ecs_cluster | Name of the ECS cluster to deploy the service to, e.g. `naro-bff-7b5b24b` | yes | — |
| ecs_service | Name of the ECS service to deploy, e.g. `bff-8c13d47`. If missing, no service deploy is attempted. | no | SKIP |
| slack_webhook_url | Slack webhook URL for reporting deploy failures/successes | yes | — |
| dockerfile_path | Optional path to the dockerfile for building this image, e.g. `./bff/dockerfile` | no | ./Dockerfile |
| container_name | Optional name of the container to update when deploying, e.g. `web` | no | web |
| push_image | Optional flag that controls whether to push a container image or just assume it already exists. Useful if you need to deploy to multiple tasks from the same image; the first deploy should publish the container while the rest shouldn't. | no | yes |
Outputs
no outputs