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.
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:
Next, I’m thinking a copy of your deployment process JSON might be helpful for us to get some more context around how your project is configured. The following documentation page has instructions on exporting the raw deployment process out of Octopus to be attached here.
I have made this conversation private so only yourself and Octopus staff are able to view it and any attachments.
If you have any further questions or thoughts here, please don’t hesitate to let me know.
@Daniel_Fischer, I found the issue. I needed to update the command in the script. That seemed to get the rest of the job working and targeting the right files. Let me know there is any additional information I can provide that would be more helpful to the community.