vaibhavn
9 September 2021 01:12
1
I am using Octopus Cloud. I continue to get below warning even after migrating from Octopus worker to an execution container with custom docker image where I have my own version of AWS CLI. Can this warning be removed or is there a way I can suppress/ignore this warning in deployment logs.
Using the AWS tools bundled with Octopus is not recommended. Learn more about AWS Tools at https://g.octopushq.com/AWSTools .
Hi @vaibhavn ,
Thanks for getting in touch! Sorry to see you’re hitting this issue. Fortunately this is a known bug that I’ll link to below. The fix for it will be shipped in the upcoming release v2021.2.7454.
opened 01:36PM - 27 Aug 21 UTC
closed 10:43PM - 01 Sep 21 UTC
kind/bug
area/steps
# Prerequisites
- [x] I have verified the problem exists in the latest versio… n
- [x] I have searched [open](https://github.com/OctopusDeploy/Issues/issues) and [closed](https://github.com/OctopusDeploy/Issues/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed) issues to make sure it isn't already reported
- [x] I have written a descriptive issue title
- [x] I have linked the original source of this report
- [x] I have labelled the value stream (area/core, area/steps, ...)
- [x] I have tagged the issue appropriately (kind/bug, kind/enhancement, feature/ ...)
# The bug
'Run an AWS CLI script' steps which use the AWS tools on a worker created before upgrading to 2021.2 do not contain the flag `'OctopusUseBundledTooling = "false"'` as a result, even when using worker tools, the warning message `Using the AWS tools bundled with Octopus is not recommended. Learn more about AWS Tools at https://g.octopushq.com/AWSTools.` shows up as a false positive.
## What I expected to happen
The check to display the warning message would look specifically for `OctopusUseBundledTooling = 'True'` rather than the lack of a flag.
This would mean that steps created even before the change wouldn't show this warning message.
## Steps to reproduce
Reproducing this warning without running 2021.1 and upgrading requires some API manipulation as creating the issue organically is impossible due to newly created steps having the 'False' flag.
1. Create a project with a 'Run an AWS CLI script' step.
2. Configure it to use the AWS tools running on a worker.
3. Open the API to show the process steps for this project.
4. Copy the API process steps and remove the 'OctopusUseBundledTooling' flag.
5. PUT these new process settings to the project via the API
6. Run the project and observe the warning message.
### Screen capture
### Log excerpt
```
Using the AWS tools bundled with Octopus is not recommended. Learn more about AWS Tools at https://g.octopushq.com/AWSTools.
```
## Affected versions
**Octopus Server:2021.2.X**
## Workarounds
You can remove the warning by opening the process step and de-selecting 'Run inside a container', then swapping the setting for the tooling to use those on a worker, then saving the project. After, you would then re-select 'Run inside a container' and configure the container as appropriate.
Alternatively, you can add the `OctopusUseBundledTooling = 'False'` flag via API.
## Links
Cloud repro: https://octopus-operations.octopus.app/app#/Spaces-262/projects/aws-cli-warning-repro/deployments
The above bug report also lists a couple potential workarounds.
You can remove the warning by opening the process step and de-selecting ‘Run inside a container’, then swapping the setting for the tooling to use those on a worker, then saving the project. After, you would then re-select ‘Run inside a container’ and configure the container as appropriate.
I hope this helps, and please let us know if you have any questions or concerns going forward!
Best regards,
Kenny
system
10 October 2021 01:38
4
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.