Madhav Puri 54240f8da9 Support for passing build-time variables in build context ... - The build-time variables are passed as environment-context for command(s) run as part of the RUN primitve. These variables are not persisted in environment of intermediate and final images when passed as context for RUN. The build environment is prepended to the intermediate continer's command string for aiding cache lookups. It also helps with build traceability. But this also makes the feature less secure from point of view of passing build time secrets. - The build-time variables also get used to expand the symbols used in certain Dockerfile primitves like ADD, COPY, USER etc, without an explicit prior definiton using a ENV primitive. These variables get persisted in the intermediate and final images whenever they are expanded. - The build-time variables are only expanded or passed to the RUN primtive if they are defined in Dockerfile using the ARG primitive or belong to list of built-in variables. HTTP_PROXY, HTTPS_PROXY, http_proxy, https_proxy, FTP_PROXY and NO_PROXY are built-in variables that needn't be explicitly defined in Dockerfile to use this feature. Signed-off-by: Madhav Puri <madhav.puri@gmail.com>		2015-09-16 03:31:15 -07:00
..
dumper
testfiles	builder: avoid decoding "null" string in ADD, COPY and VOLUME step to nil slice	2015-08-18 21:15:57 +09:00
testfiles-negative
json_test.go
line_parsers.go	Support for passing build-time variables in build context	2015-09-16 03:31:15 -07:00
parser.go	Support for passing build-time variables in build context	2015-09-16 03:31:15 -07:00
parser_test.go	Support for passing build-time variables in build context	2015-09-16 03:31:15 -07:00
utils.go	Fix golint warnings for builder	2015-07-22 13:29:03 +08:00