Hello Friendly Neighborhood Octopus Support/Community,
When using the RUN AN AWS CLI SCRIPT step Template. We are noticing weird behaviors with a default Compress mechanism. This is preventing us from properly packaging the built solution and running deployments to the BeanStalk instance.
Little background, we are trying to deploy a solution to AWS BeanStalk following this guide https://octopus.com/blog/deploy-to-aws-beanstalk.
When we switch to a new referenced package Octopus Deploy starts adding every package on the server and fails to deploy due to zip conflicts. This is not what we expect to happen, we are wanting just the referenced package to be apart of the package sent to Octopus, not having Octopus find every package within the C drive. This happens, when we clone the existing project that works and only update the referenced package.
Issue images of updated package reference, package reference configuration, package ID in Octopus Library:
No issues images when using default RandomQuotes, updated package reference, package reference configuration, package ID in Octopus Library: