You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implemented possibility to override custom properties during runtime. (#7)
It is for example possible to invoke the build with additional properties in such way:
docker-bakery build ... --property foo1=bar1 --property foo2=bar2
Usage: "Optional. Used to override rootDir of the dockerfiles location. Can be defined in config.json, provided in this argument or determined dynamically from the base dir of config file.",
32
32
},
33
+
cli.StringSliceFlag{
34
+
Name: "property, p",
35
+
Usage: "Optional. Allows for providing additional multiple properties that can be used during templating. Overrides properties defined in config.json file. Expected format is: -p propertyName=propertyValue",
36
+
},
33
37
},
34
38
Usage: "Used to fill Dockerfile.template file. Values needed for template are taken from the config file and from dynamic properties provided during runtime.",
Usage: "Optional. False be default. If this flag is set build of the parent will not trigger dependant builds.",
61
65
},
66
+
cli.StringSliceFlag{
67
+
Name: "property, p",
68
+
Usage: "Optional. Allows for providing additional multiple properties that can be used during templating. Overrides properties defined in config.json file. Expected format is: -p propertyName=propertyValue",
69
+
},
62
70
},
63
71
Usage: "Used to build next version of the images in given scope. Optionally it can skip build of dependant images.",
0 commit comments