Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CASMCMS-8164: Improve BOS documentation #5722

Merged
merged 2 commits into from
Feb 6, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion operations/boot_orchestration/Session_Templates.md
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ The following S3 parameters are used to specify this file:
* path: This is the path to the `manifest.json` file in S3. The path will follow the `s3://<BUCKET_NAME>/<KEY_NAME>` format.
* `<BUCKET_NAME>` is set to `boot-images`
* `<KEY_NAME>` is set to the image ID that the [Image Management Service (IMS)](../../glossary.md#image-management-service-ims) created when it generated the boot artifacts.
* `etag`: This entity tag helps identify the version of the `manifest.json` file. Currently, it issues a warning if the manifest's `etag` does not match. This can be an empty string, but cannot be left blank.
* `etag`: This entity tag helps identify the version of the `manifest.json` file. Its value can be an empty string, but cannot be left blank. However, the `etag` line can be omitted entirely.

This boot artifact information from the files stored in S3 is then written to the
[Boot Script Service (BSS)](../../glossary.md#boot-script-service-bss) where it is retrieved when these nodes boot.
Expand Down