Andrew Sy Kim

> Should --persist be on by default? > Is there a more evocative name than persist? Regarding the `--persist` flag, I wonder if it's worth making a distinction between these...

Perhaps one solution is to always assume the build context is the current directory but add a `-f` flag to set the relative path to the Earthfile. This way you...

> Or perhaps make it even more explicit instead with --context, -c set to the path where you want the context to be run from. That way it is still...

I think a `--context` flag or similar makes sense and seems useful as long as we preserve the default behavior of assuming the current directory for simplicity.

After mulling over this for a few hours, I think we need to give this more thought. Being able to set the local context can be useful for many cases...

One potential route we can take here is to just allow `COPY` to reference files in parent directories. ``` build: FROM +base COPY --dir ../src . ``` This way the...

@bkendzior @ypgs @mvgijssel appreciate the feedback! I think we should be able to implement COPY-ing parent directories such that we only expand the build context to include the relevant files...

Just speaking out loud here. Maybe features that touch the core tree should follow the same enhancement processes until they are fully removed? Anything fully "out-of-tree" can have its own...

Worth noting that we have a current proposal for this topic w.r.t external cloud providers https://github.com/kubernetes/enhancements/pull/1727

I think this warrants a page in the official Kubernetes docs, @onitake are you willing to put something together?