Skip to content
Open
Show file tree
Hide file tree
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
8 changes: 0 additions & 8 deletions cmd/quarry-sysupdate/update.go
Original file line number Diff line number Diff line change
Expand Up @@ -24,14 +24,6 @@ var updateCommand = withExtensionDirFlag(withQuarryUserFlag(withQuarryProxyFlag(
&xsysupdate.TransferFileExtension{
OverrideSourcePathURL: ctxQuarryProxyURL(ctx),
},
&xsysupdate.TagsExtension{
// TODO: There is no ownership model for machine tags yet, so
// as a temporary workaround we take full control of the acp.*
// and amutable.* tag namespaces. These tags always exactly
// match the set shipped by the configured repositories, and
// tags outside them are never touched.
AllowedNamespaces: []string{"acp.", "amutable."},
},
}
ctx, err := exts.DoInit(ctx)
if err != nil {
Expand Down
6 changes: 6 additions & 0 deletions contrib/systemd/quarry-sysupdate.service
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,12 @@
Description=Quarry-Based Automatic System Update
Wants=network-online.target
After=network-online.target
# Features gated on machine tags (SuggestOnMachineTag=) become enabled only
# when `systemd-sysupdate enable-feature --feature-suggested` runs, which is
# what systemd-sysupdate-auto-enable.service does. Run it ahead of every
# update: a tag that arrives with this run's confext is picked up by the next.
Wants=systemd-sysupdate-auto-enable.service
After=systemd-sysupdate-auto-enable.service

# For containers we assume that the manager will handle updates. And we likely
# can't even access our backing block device anyway.
Expand Down
4 changes: 2 additions & 2 deletions docs/getting-started.md
Original file line number Diff line number Diff line change
Expand Up @@ -392,8 +392,8 @@ directly, but for those who are interested:
local HTTP server as a source in transfer files.

* `quarry sysupdate update` wraps `systemd-sysupdate` and does some pre-update
and post-update steps (such as installing tags and instantiating transfer
files from the TUF repository).
and post-update steps (such as instantiating transfer files from the TUF
repository).

In most cases, you should avoid interacting with these tools -- these are
intended to be used by a `systemd-sysupdate`-managed operating system directly.
Expand Down
Loading