aws-cli-docker icon indicating copy to clipboard operation
aws-cli-docker copied to clipboard

Published 20 hours ago • verified publisher icon mikesir87

Set entrypoint to aws

Open shnhrrsn opened this issue 5 years ago • 1 comments

Any chance you can update to use the entrypoint as aws? It'd be helpful to use with whalebrew which requires it: https://github.com/bfirsh/whalebrew#creating-packages

I'm currently using mesosphere/aws-cli with whalebrew, but it’s not kept up to date and I’d like to switch :)

Thanks!

shnhrrsn avatar Feb 27 '19 04:02 shnhrrsn

Hi @shnhrrsn! This was actually a deliberate decision to not make aws as the entrypoint. The reasoning was to make it easier to do workflows in CI builds where you might need to get data, use jq to change things, and then send it back to AWS.

However, I think it would be awesome to support whalebrew. One thought I have is to actually turn the Dockerfile into a multi-stage build in which one stage sets the entrypoint. Then, I can update the build to produce two images. Something like this...

  • latest, 1.16.113, etc. - work as is
  • latest-e, 1.16.113-e, etc. - have the entrypoint set.

Basically, any image tags with a -e suffix have the entrypoint set. Thoughts?

mikesir87 avatar Feb 27 '19 20:02 mikesir87