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.

Sign up for GitHub

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

Jump to bottom

Clarify use case for update repos #1339

Merged
merged 2 commits into from
Feb 23, 2021
Merged

Clarify use case for update repos #1339

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d405a0e
Clarifications about update repos
gregdek Feb 22, 2021
ebb68a8
Update PUBLISHING.md
gregdek Feb 22, 2021
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
3 changes: 2 additions & 1 deletion PUBLISHING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,10 +79,11 @@ cargo make revoke-ami -e REVOKE_FROM_USERS=0123456789,9876543210

## Build a repo

> NOTE: If you intend to replace hosts rather than update them, you don't need to build an update repository.

Bottlerocket uses [TUF repositories](https://theupdateframework.io/overview/) to make system updates available to hosts.
You can read more about how Bottlerocket uses TUF in the [updater README](sources/updater/README.md#tuf-and-tough).

If you plan to update hosts rather than replace them, you'll need to make a repo.
Initially, the repo will only contain the image you just built.
Later, when you build updates, you can [add them to the repo](#configuring-your-repo-location), which allows your hosts to update to new versions.
(If you don't have an `Infra.toml` file, it will always try to build a brand new repo.)
Expand Down