Add generic example

iamhopaul123 · iamhopaul123 · commit a79e7b79f88a · 2020-06-22T16:21:39.000-07:00
diff --git a/docs/features.md b/docs/features.md
@@ -58,4 +58,4 @@ However, compared to V3, V4 includes additional network metadata when querying t
 
 #### Generic Metadata Injection
 
-As mentioned above in the previous section, to inject generic metadata, you'll need to have those additional metadata in JSON files. Then specify paths for the JSON files by using `CONTAINER_METADATA_PATH` and `TASK_METADATA_PATH` environment variables. More specifically, `CONTAINER_METADATA_PATH` is the extra metadata for each container, which will override their counterparts in the normal response. Also, `TASK_METADATA_PATH` is for task level metadata, which is used for top level fields describing the task that are not in the containers list.
+As mentioned above in the previous section, to inject generic metadata, you'll need to have those additional metadata in JSON files. Then specify paths for the JSON files by using `CONTAINER_METADATA_PATH` and `TASK_METADATA_PATH` environment variables. More specifically, `CONTAINER_METADATA_PATH` is the metadata for each container, which will override their counterparts in the normal response. Also, `TASK_METADATA_PATH` is for task level metadata, which is used only for overriding the top level fields in the task metadata response. If you specify both `CONTAINER_METADATA_PATH` and `TASK_METADATA_PATH`, then the metadata from `CONTAINER_METADATA_PATH` will be included in the `Containers` section of the task metadata response. See example for overriding task metadata response [here](../example/generic).
diff --git a/examples/generic/task-metadata.json b/examples/generic/task-metadata.json
@@ -1,6 +1,6 @@
 {
-  "Cluster": "arn:aws:ecs:us-west-2:&ExampleAWSAccountNo1;:cluster/default",
-  "TaskARN": "arn:aws:ecs:us-west-2:&ExampleAWSAccountNo1;:task/default/febee046097849aba589d4435207c04a",
+  "Cluster": "arn:aws:ecs:us-west-2:ExampleAWSAccountNo1;:cluster/default",
+  "TaskARN": "arn:aws:ecs:us-west-2:ExampleAWSAccountNo1;:task/default/febee046097849aba589d4435207c04a",
   "Family": "query-metadata",
   "Revision": "7",
   "DesiredStatus": "RUNNING",
@@ -11,5 +11,5 @@
   },
   "PullStartedAt": "2020-03-26T22:25:40.420726088Z",
   "PullStoppedAt": "2020-03-26T22:26:22.235177616Z",
-  "AvailabilityZone": "us-west-2c",
+  "AvailabilityZone": "us-west-2c"
 }

Original file line number	Diff line number	Diff line change
`@@ -58,4 +58,4 @@ However, compared to V3, V4 includes additional network metadata when querying t`
`58`	`58`
`59`	`59`	`#### Generic Metadata Injection`
`60`	`60`
`61`		-As mentioned above in the previous section, to inject generic metadata, you'll need to have those additional metadata in JSON files. Then specify paths for the JSON files by using `CONTAINER_METADATA_PATH` and `TASK_METADATA_PATH` environment variables. More specifically, `CONTAINER_METADATA_PATH` is the extra metadata for each container, which will override their counterparts in the normal response. Also, `TASK_METADATA_PATH` is for task level metadata, which is used for top level fields describing the task that are not in the containers list.
	`61`	+As mentioned above in the previous section, to inject generic metadata, you'll need to have those additional metadata in JSON files. Then specify paths for the JSON files by using `CONTAINER_METADATA_PATH` and `TASK_METADATA_PATH` environment variables. More specifically, `CONTAINER_METADATA_PATH` is the metadata for each container, which will override their counterparts in the normal response. Also, `TASK_METADATA_PATH` is for task level metadata, which is used only for overriding the top level fields in the task metadata response. If you specify both `CONTAINER_METADATA_PATH` and `TASK_METADATA_PATH`, then the metadata from `CONTAINER_METADATA_PATH` will be included in the `Containers` section of the task metadata response. See example for overriding task metadata response [here](../example/generic).