Skip to content

Commit b606eb0

Browse files
committed
Merge branch 'release/1.14.0'
2 parents c84304e + 4d87a3a commit b606eb0

File tree

6 files changed

+325
-94
lines changed

6 files changed

+325
-94
lines changed

README.rst

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -258,6 +258,22 @@ Instead of setting environment variables separately, you can pass a .env file pe
258258

259259
$ ecs deploy my-cluster my-service --s3-env-file my-app arn:aws:s3:::my-ecs-environment/my-app.env
260260

261+
Set secrets via .env files
262+
==============================
263+
Instead of setting secrets separately, you can pass a .env file per container to set all secrets at once.
264+
265+
This will expect an env file format, but any values will be set as the `valueFrom` parameter in the secrets config.
266+
This value can be either the path or the full ARN of a secret in the AWS Parameter Store. For example, with a secrets.env
267+
file like the following:
268+
269+
```
270+
SOME_SECRET=arn:aws:ssm:<aws region>:<aws account id>:parameter/KEY_OF_SECRET_IN_PARAMETER_STORE
271+
```
272+
273+
$ ecs deploy my-cluster my-service --secret-env-file webserver env/secrets.env
274+
275+
This will modify the **webserver** container definition and add or overwrite the environment variable `SOME_SECRET` with the value of the `KEY_OF_SECRET_IN_PARAMETER_STORE` in the AWS Parameter Store of the AWS Systems Manager.
276+
261277

262278
Set a docker label
263279
===================
@@ -422,6 +438,21 @@ This instructs ecs-deploy to wait for ECS to finish the deployment for the given
422438

423439
To run a deployment without waiting for the successful or failed result at all, set ``--timeout`` to the value of ``-1``.
424440

441+
442+
Multi-Account Setup
443+
===================
444+
If you manage different environments of your system in multiple differnt AWS accounts, you can now easily assume a
445+
deployment role in the target account in which your ECS cluster is running. You only need to provide ``--account``
446+
with the AWS account id and ``--assume-role`` with the name of the role you want to assume in the target account.
447+
ecs-deploy automatically assumes this role and deploys inside your target account:
448+
449+
Example::
450+
451+
$ ecs deploy my-cluster my-service --account 1234567890 --assume-role ecsDeployRole
452+
453+
454+
455+
425456
Scaling
426457
-------
427458

ecs_deploy/__init__.py

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
VERSION = '1.13.1'
1+
VERSION = '1.14.0'

0 commit comments

Comments
 (0)