PR #1408 adds ch-image modify to modify existing images interactively or non-interactively. In the non-interactive case, the program will create a parse tree under the hood analogous to those produced by parsing Dockerfiles during ch-image build. After parsing a Dockerfile, ch-image build will "pretty print" the resulting parse tree at the verbose level, e.g.
The way we construct the parse tree under the hood is not amicable to pretty printing, which also means that we can't easily validate parse trees in the test suite. We should:
Change how we construct ch-image modify parse trees so they can be pretty printed, and
Use pretty printing to validate that one or more example trees are what we expect as part of the test suite
Note that I'm deferring this as a future issue so it doesn't further delay the PR.
PR #1408 adds
ch-image modify
to modify existing images interactively or non-interactively. In the non-interactive case, the program will create a parse tree under the hood analogous to those produced by parsing Dockerfiles duringch-image build
. After parsing a Dockerfile,ch-image build
will "pretty print" the resulting parse tree at the verbose level, e.g.The way we construct the parse tree under the hood is not amicable to pretty printing, which also means that we can't easily validate parse trees in the test suite. We should:
ch-image modify
parse trees so they can be pretty printed, andNote that I'm deferring this as a future issue so it doesn't further delay the PR.