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
Copy file name to clipboardExpand all lines: docs/30-configuration/34-jobs.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,6 +81,10 @@ jobs: [
81
81
"app",
82
82
"prod"
83
83
],
84
+
meta: {
85
+
keyA:"A",
86
+
keyB:"B",
87
+
},
84
88
interfaces: [
85
89
"eth0",
86
90
"eth1[1]",
@@ -241,6 +245,10 @@ The `initial_status` field is optional and specifies which status to immediately
241
245
242
246
The `tags` field is an optional array of tags to be used when the job is registered as a service in Consul. Other containers can use these tags in `watches` to filter a service by tag.
243
247
248
+
##### `meta`
249
+
250
+
The `meta` field is an optional map key/value to be used when the job is registered as a service in Consul. Key names must be valid JSON5/Ecmascript identifierNames or be quoted and follow consul limitation , practical this means only [a-zA-Z0-9_-] can be used in key names and key names with '-' must be quoted
251
+
244
252
##### `interfaces`
245
253
246
254
The `interfaces` field is an optional single or array of interface specifications. If given, the IP of the service will be obtained from the first interface specification that matches. (Default value is `["eth0:inet"]`). The value that ContainerPilot uses for the IP address of the interface will be set as an environment variable with the name `CONTAINERPILOT_{JOB}_IP`. See the [environment variables](./32-configuration-file.md#environment-variables) section.
0 commit comments