3 Commits

Author	SHA1	Message	Date
Colin Walters	bfd39aecf3	status: Rework auto-update status display ... First, split it into its own section; it's important enough to merit it. Second, explicitly reference the systemd timer/service units. For example, a question I often have is "when is the next run" and of course you can get that rpm `systemctl status rpm-ostreed-automatic.timer` but you have to know that, and the reminder helps. (I briefly looked at implementing the `Trigger` line from `systemctl status` but it's not entirely trivial...tempting to just fork off a `systemctl status | grep `) Prep for unifying this text with the message we print when one does `rpm-ostree upgrade` when auto-updates are enabled. Closes: #1432 Approved by: jlebon	2018-07-10 13:26:37 +00:00
Colin Walters	26f04595b2	upgrade: Note if automatic updates are enabled ... When e.g. FAH does the automatic update transition, let's remind people who are doing it manually still. Closes: #1399 Approved by: jlebon	2018-06-11 18:46:58 +00:00
Colin Walters	8387f1c7c3	Add "ex-stage" update policy, support for ostree staged deployments ... Following up to https://github.com/projectatomic/rpm-ostree/pull/1352 AKA 506910d930 which added an experimental flag to globally enable deployment staging, let's add an `ex-stage` automatic update policy. I chose to create a new `test-autoupdate-stage.sh` and rename the previous one to `test-autoupdate-check.sh` in going with the previous theme of smaller test files; it's way faster to iterate on new tests when it's a new file. And adding staging at the top would have been weird. This was all quite straightforward, just plumbing through lots of layers. Closes: #1321 Approved by: jlebon	2018-05-14 19:03:56 +00:00