cloudposse/Deploy Ecspresso
Deploy ECS with Ecspresso
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| image | Docker image | yes | — |
| image-tag | Docker image tag | yes | — |
| debug | Debug mode | no | false |
| region | AWS Region | yes | — |
| operation | Operation (valid options - `deploy`, `destroy`) | yes | deploy |
| cluster | Cluster name | yes | — |
| ecspresso-version | Ecspresso version | no | v2.1.0 |
| application | Application name | yes | — |
| taskdef-path | Task definition path | yes | — |
| timeout | Ecspresso timeout | no | 5m |
| mirror_to_s3_bucket | Mirror task definition to s3 bucket | no | — |
| use_partial_taskdefinition | NOTE: Experimental. Load templated task definition from S3 bucket, which is created by the `ecs-service` component. This is useful when you want to manage the task definition in the infrastructure repository and the application repository. The infrastructure repository manages things like Volumes and EFS mounts, and the Application repository manages the application code and environment variables. | no | — |
Outputs
| name | description |
|---|---|
| webapp-url | Web Application url |