I actually have a project that I created yesterday, so no need to create a new project, and it is not displaying warnings. Several of the steps in this process were cloned from another project that is now displaying warnings.
I’ve pulled out the deployment process for both of those steps via the API, and I can see that in the new project created yesterday the steps do have the property
OctopusUseBundledTooling: "False". When changing in the UI to run on a worker rather than in a container, the option for the new project is to use tools on the worker, which is now the default, whereas older projects have the option to use bundled tools. So I’m guessing that as well as the displaying the unwanted warning, the updated changed the default option for AWS tools.
So while I now understand what has happened and why it’s happened, please know that this is undesirable and will cause a lot of work. Not only will we have to check every single project for “Run an AWS CLI Script” steps and update them, we’ll also have to revalidate those projects. And for any old releases that contain a process snapshot where
OctopusUseBundledTooling: "False" is missing, we’ll have to engage QA to inspect logs and ensure that the unwanted Octopus warning isn’t masking any genuine warnings that we need to be concerned about.
Long story short, please remove this warning. It’s not necessary for two reasons -
- You warn in the Octopus UI
- We’re not even using the bundled tools because we’re running in a Docker container, so it shouldn’t matter.