Package Exports
- @eclass/semantic-release-ecs-deploy
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@eclass/semantic-release-ecs-deploy) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
@eclass/semantic-release-ecs-deploy
semantic-release plugin to deploy ecs services
| Step | Description |
|---|---|
verifyConditions |
Verify the presence of the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variable. |
publish |
Upgrade service in aws ecs. |
Install
npm i -D @eclass/semantic-release-ecs-deployUsage
The plugin can be configured in the semantic-release configuration file:
{
"plugins": [
"@semantic-release/changelog",
"@semantic-release/npm",
"@semantic-release/git",
"@semantic-release/gitlab",
[
"@eclass/semantic-release-ecs-deploy",
{
"cluster": "mycluster",
"service": "myservice",
}
]
]
}Configuration
Environment variables
| Variable | Description |
|---|---|
AWS_ACCESS_KEY_ID |
aws access key id |
AWS_SECRET_ACCESS_KEY |
aws secret access key |
Options
| Variable | Description |
|---|---|
cluster |
Name of cluster in aws ecs. Required. |
service |
Name of service in aws ecs. Required. |
Examples
{
"plugins": [
"@semantic-release/changelog",
"@semantic-release/npm",
"@semantic-release/git",
"@semantic-release/gitlab",
[
"@eclass/semantic-release-ecs-deploy",
{
"cluster": "mycluster",
"service": "myservice",
}
]
]
}# .gitlab-ci.yml
release:
image: node:alpine
stage: release
script:
- npx semantic-release
only:
- master# .travis.yml
language: node_js
cache:
directories:
- ~/.npm
node_js:
- "12"
stages:
- test
- name: deploy
if: branch = master
jobs:
include:
- stage: test
script: npm t
- stage: deploy
script: npx semantic-release