Issue #, if available:
Related to #30 but this is just a quick fix, not full support for volumes
Description of changes:
With the release of EFS support in Fargate I tried to deploy to a service with a mounted volume. But I got the error that the volume name didn't exist and after running with --verbose I noticed it just wasn't sent along with the task definition.
This PR passes through the volumes part of the task definition so that fargate service deploy still works when a task has volumes.
It also updates the AWS SDK because the previous version did not support the EFS configuration of volumes in task definitions so the information was lost in updates.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Issue #, if available: Related to #30 but this is just a quick fix, not full support for volumes
Description of changes: With the release of EFS support in Fargate I tried to deploy to a service with a mounted volume. But I got the error that the volume name didn't exist and after running with
--verboseI noticed it just wasn't sent along with the task definition.This PR passes through the volumes part of the task definition so that
fargate service deploystill works when a task has volumes.It also updates the AWS SDK because the previous version did not support the EFS configuration of volumes in task definitions so the information was lost in updates.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.