Orb circleci/aws-cli is not really the aws cli? 'eks' command missing

#1

I use

orbs:
  aws-cli: circleci/aws-cli@0.1.13

from https://circleci.com/orbs/registry/orb/circleci/aws-cli#quick-start

which complete successfully:

Successfully installed PyYAML-3.13 awscli-1.16.152 botocore-1.12.142 colorama-0.3.9 docutils-0.14 futures-3.2.0 jmespath-0.9.4 pyasn1-0.4.5 python-dateutil-2.8.0 rsa-3.4.2 s3transfer-0.2.0

awscli-1.16.152 looks good

but then I try to use aws eks and I get the error:

- run: aws eks update-kubeconfig --name erp-app-cluster

Invalid choice: 'eks', maybe you meant:

  * es

Orb are super confusing to me, why is eks not available? I have the same version on my Mac and for sure eks is available…

#2

Hi @phil-lgr, please see the orb description:

Install and configure the AWS command-line interface (awscli)

Our orb is not a complete wrapper around the AWS CLI—it just installs and configures it.

From there, you can run any regular awscli command in a normal CircleCI run step, etc.

Thank you!

#3

From there, you can run any regular awscli command in a normal CircleCI run step, etc.

well when I run:

- run: aws eks update-kubeconfig --name erp-app-cluster

I get:

Invalid choice: 'eks', maybe you meant:

  * es

it’s like the aws eks command is not there!

#4

my aws setup step looks like this:

  #
  # install and configure aws-cli
  #
  aws_cli_setup:
    working_directory: ~/repo
    executor: aws-cli/default
    steps:
      - aws-cli/install
      - aws-cli/configure:
          profile-name: circle-ci
          aws-access-key-id: AWS_ACCESS_KEY_ID
          aws-secret-access-key: AWS_SECRET_ACCESS_KEY
          aws-region: AWS_REGION
      - aws-ecr/ecr-login:
          region: AWS_REGION      
#5

Our orb is not a complete wrapper around the AWS CLI

Could you add what is not available in the orb description then?

#6

Hi @phil-lgr, sounds like this is a common issue:

#7

The orb just installs and configures the AWS CLI. It doesn’t do anything besides that. Any AWS CLI commands should be available for you to run normally, though.

#8

Before opening a ticket here I googled for a good hour trying to see what could be wrong — I did double check the version:

#9

during the config step:

#10

@phil-lgr Feel free to file a GitHub issue against the orb repository:

Seems like this is an upstream issue:

But perhaps we can still remedy it by changing how we install the AWS CLI in our orb.

Thanks!

#11

@phil-lgr Have you verified that eks functionality is available in v1.11.165 of the AWS CLI?

#12
Philippes-iMac:erp-app phil$ aws --version
aws-cli/1.16.150 Python/3.7.3 Darwin/18.5.0 botocore/1.12.140
Philippes-iMac:erp-app phil$ aws eks
usage: aws [options] <command> <subcommand> [<subcommand> ...] [parameters]
To see help text, you can run:

  aws help
  aws <command> help
  aws <command> <subcommand> help
aws: error: the following arguments are required: operation
#13

when I use the aws-cli orb, I am supposed to be able to use aws anywhere?

how is it possible that the installed version during:

  aws_cli_setup:
    working_directory: ~/repo
    executor: aws-cli/default
    steps:
      - aws-cli/install

does not match the one when I do aws --version in my build?

#14

I don’t know. Please file an issue against the orb repository. Thanks!

#15

Ahh, sorry @phil-lgr, the repo for this orb is actually here:

#16

Resolved; aws commands need to be run in the same job as the aws-cli/install and aws-cli/configure commands:

1 Like
closed #17

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.