Update concourse docker resource schema

See: https://github.com/spring-projects/sts4/issues/197
This commit is contained in:
Kris De Volder
2019-02-05 16:19:41 -08:00
parent c8abce640a
commit 57fb7e1e2e
7 changed files with 49 additions and 14 deletions

View File

@@ -515,6 +515,8 @@ public class PipelineYmlSchema implements YamlSchema {
addProp(put, "cache_tag", t_ne_string);
addProp(put, "dockerfile", t_ne_string);
addProp(put, "import_file", t_ne_string);
addProp(put, "labels", t_string_params);
addProp(put, "labels_file", t_ne_string);
addProp(put, "load", t_ne_string);
addProp(put, "load_base", t_ne_string);
addProp(put, "load_bases", t_strings);
@@ -523,7 +525,9 @@ public class PipelineYmlSchema implements YamlSchema {
addProp(put, "load_tag", t_ne_string);
addProp(put, "pull_repository", t_ne_string).isDeprecated(true);
addProp(put, "pull_tag", t_ne_string).isDeprecated(true);
addProp(put, "tag", t_ne_string);
addProp(put, "tag", t_ne_string).isDeprecated(true);
addProp(put, "tag_file", t_ne_string);
addProp(put, "tag_as_latest", t_boolean);
addProp(put, "tag_prefix", t_ne_string);
addProp(put, "target_name", t_ne_string);

View File

@@ -1,10 +1,15 @@
*Optional.* A map of Docker build arguments.
*Optional.* A map of Docker build-time variables. These will be available as environment variables during the Docker build.
While not stored in the image layers, they are stored in image metadata and so it is recommend to avoid using these to pass secrets into the build context. In multi-stage builds ARGs in earlier stages will not be copied to the later stages, or in the metadata of the final stage.
The [build metadata](https://concourse-ci.org/implementing-resources.html#resource-metadata) environment variables provided by Concourse will be expanded in the values (the syntax is `$SOME_ENVVAR` or `${SOME_ENVVAR}`).
Example:
```yaml
```
build_args:
do_thing: true
how_many_things: 2
email: me@yopmail.com
```
DO_THING: true
HOW_MANY_THINGS: 2
EMAIL: me@yopmail.com
CI_BUILD_ID: concourse-$BUILD_ID
```

View File

@@ -0,0 +1,9 @@
*Optional*. A map of labels that will be added to the image.
Example:
```
labels:
commit: b4d4823
version: 1.0.3
```

View File

@@ -0,0 +1,7 @@
*Optional*. Path to a JSON file containing the image labels.
Example file contents:
```
{ "commit": "b4d4823", "version": "1.0.3" }
```

View File

@@ -1,2 +1 @@
*Optional.* The value should be a path to a file containing the name
of the tag.
**DEPRECATED - Use `tag_file` instead**

View File

@@ -0,0 +1 @@
*Optional*. The value should be a path to a file containing the name of the tag.