docs: rm description re: AWS CLI installations #314
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes the commands & jobs' descriptions re: AWS CLI installations.
As of v9.x, the commands & jobs do not explicitly install AWS CLI by default.
Rather, it is assumed that the executor chosen would have the AWS CLI already installed.
For instance, the
aws-ecr/default
executor is theubuntu-2004:2022.04.2
Machine executor, which comes pre-installed with AWS CLI.I understand that alternatively, users can ensure the AWS CLI is installed via:
auth
parameter's steps when using the build_and_push_image job, orpre-steps
if neededChecklist
Motivation, issues
Description