Skip to content

Commit cd64e42

Browse files
trishankatdatadogjeremyrickard
authored andcommitted
Clarify why bundle.json is mounted in the invocation image (#228)
* clarify why bundle.json is mounted in the invocation image Signed-off-by: Trishank K Kuppusamy <trishank.kuppusamy@datadoghq.com> * remove link
1 parent dda27cb commit cd64e42

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

101-bundle-json.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ A `bundle.json` is broken down into the following categories of information:
2626
- A list of outputs (name, type and location) that the application produces
2727
- A set of schema definitions used to validate user input
2828

29-
The `bundle.json` is located at `/cnab/bundle.json` in the invocation image's runtime filesystem.
29+
The bundle definition is made accessible from inside the invocation image in order to allow the run tool to reference information in the file. The bundle.json MUST be mounted to /cnab/bundle.json.
3030

3131
The `bundle.json` is also known as a _thin bundle_. Bundles come in two formats: thick and thin. Read more about thick and thin bundles in the [bundle formats section](104-bundle-formats.md).
3232

0 commit comments

Comments
 (0)