-
Notifications
You must be signed in to change notification settings - Fork 196
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
Add new D-Bus APIs for deployment finalization #1814
Conversation
126bf71
to
7d8269b
Compare
Ready for review! |
7d8269b
to
081bee4
Compare
Requires: ostreedev/ostree#1841 |
bot, retest this please |
(Test failure was due to rdgo being broken and testing against a libostree without ostreedev/ostree#1841. Should be fixed now!) |
081bee4
to
b9ec996
Compare
Fixup! ⬆️ I also changed the transaction type name to |
LGTM, just
|
This also looks fine to me, but I guess it needs a rebase to master. |
Teach `UpdateDeployment` to make use of libostree's staging lock and then add a `FinalizeDeployment` API to perform the final unlock & reboot. I also added a hidden CLI to make testing this easier, but also because it's likely the FCOS-agent-yet-to-be-named will just end up using the CLI to keep it simple. Closes: coreos#1748
b9ec996
to
1b5adca
Compare
Rebased! ⬆️ |
⚡ Test exempted: pull fully rebased and already tested. |
Teach
UpdateDeployment
to make use of libostree's staging lock andthen add a
FinalizeDeployment
API to perform the final unlock &reboot.
I also added a hidden CLI to make testing this easier, but also because
it's likely the FCOS-agent-yet-to-be-named will just end up using the
CLI to keep it simple.
Closes: #1748