We’ve recently upgraded to 2019.10.5 to get access to the Package parameter type in Step Templates. I am trying to create a Step Template for updating a task definition in AWS with a new docker image. The image is being pushed to AWS outside of Octopus. It shows up correctly in the AWS ECR feed we created.
When creating a normal step in a project, I can follow the standard instructions from https://octopus.com/blog/ecs. When I click on “Reference a package”, I’m given the option “The package will not be acquired”, so that Octo doesn’t attempt to download the docker image from ECR.
However, when creating a package reference in a Step Template and let the project choose the package, that choice to acquire or not is not presented. The choice is absent both when editing the Step Template and when choosing the package in the Project.
Apparently it is choosing to acquire at all times, and since downloading images from ECR isn’t a real thing that can happen, my deploy fails. The error presented is:
“The step failed: Activity failed with error ‘The AWS Elastic Container Registry at region us-east-1 does not support downloading packages on the Octopus Server.’.”
This seems like a bug to me. The “Reference a package” screen on the Step Template edit should be almost identical to the “Reference a package” screen when editing a normal step in a Project. The “let the Project select the Package” option is unusable for AWS ECR in its current state.
Please let me know if I’ve somehow missed this setting somewhere. Since we deploy a wide variety of docker images to AWS across multiple projects, being able to reuse the script as a Step Template would be very convenient.