Write out sources into subdirectory in build context about ansible-builder HOT 5 CLOSED

Rather than putting the Dockerfile outside of the context directory. I think we should always put the stuff that’s ADDed under a sources/ directory (call it whatever).

from ansible-builder.

^ Everyone says keeping a lightweight build context is a best practice, and if you're putting the context at the top level of the project, there's going to be a bunch of who-knows-what which gets into that same folder, like .git, Zuul config, etc...

Managing a custom path for the Dockerfile might get a little ugly, but not as bad as people throwing around .dockerignores all over the place

EDIT: or maybe the "sources" directory becomes the build context... I'm not sure if that works or not, will have to think on it.

from ansible-builder.

^ Everyone says keeping a lightweight build context is a best practice, and if you're putting the context at the top level of the project, there's going to be a bunch of who-knows-what which gets into that same folder, like .git, Zuul config, etc...

Managing a custom path for the Dockerfile might get a little ugly, but not as bad as people throwing around .dockerignores all over the place

EDIT: or maybe the "sources" directory becomes the build context... I'm not sure if that works or not, will have to think on it.

I like the idea of 'sources' folder inside of context, which is where Dockerfile live. I'm going to hack on it this weekend, to see if I can come up with a POC.

from ansible-builder.

I'm tripping over terminology now. The Dockerfile doesn't need to be in the build context, so when this sources folder is proposed, it makes sense that that becomes the build context, only problem is that ansible-builder build already has a CLI option for the build context.

from ansible-builder.

Closed with #157, which finalized on the _build directory.

See awx-ee

https://github.com/ansible/awx-ee/tree/devel/_build

network-ee has also been updated.

from ansible-builder.