Support for layer caching? about aws-ecr-orb HOT 4 CLOSED

@ericf89 At the top of your .circleci/config.yml you need to define the executor:
e.g.

orbs:
  aws-ecr: circleci/[email protected]
executors:
  docker_build:
    machine:
      docker_layer_caching: true

Then in your workflow job you can specify the executor:

workflows:
  build_and_push_image:
    jobs:
      - aws-ecr/build_and_push_image:
          executor: docker_build
          account-url: AWS_ECR_ACCOUNT_URL_ENV_VAR_NAME
          aws-access-key-id: ACCESS_KEY_ID_ENV_VAR_NAME
          aws-secret-access-key: SECRET_ACCESS_KEY_ENV_VAR_NAME
          context: myContext
          create-repo: true
          dockerfile: myDockerfile
          path: pathToMyDockerfile
          profile-name: myProfileName
          region: AWS_REGION_ENV_VAR_NAME
          repo: myECRRepository
          tag: myECRRepoTag

My understanding is that Orbs can only be used within workflows.

from aws-ecr-orb.

I see that this can be accomplished via executors. Closing this issue, but for anyone looking for information on this you simply need to enable docker_layer_caching in an executor in order to enable it.

from aws-ecr-orb.

@jeffnappi Is this possible at the job level, or only by command? Still trying to figure out the syntax :/

from aws-ecr-orb.

@jeffnappi Awesome! That worked beautifully. Thanks a bunch. 🎉

I was trying to do the something like

    executor: 
        machine: 
             docker_layer_caching: true

in line in the job with no luck. Didn't know you could define those excutors externally.

I think this orb does expose a build-and-push-image command in addition to the build_and_push_image job, so you can use the command in your own job some how. But I've not been able to get that to work either, (aws-cli fails to install, also due to some other executor weirdness I think). But this solves my issue as far as I can tell.

Thanks again!

from aws-ecr-orb.