-
Notifications
You must be signed in to change notification settings - Fork 6
Add support for remote actions #76
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
Conversation
ac8e0a7 to
073c2e5
Compare
e8e364a to
e39bcb1
Compare
vkhoroz
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My only leftover comment goes to the place where we store that cached list of actions.
I'm not sure how the "feature" to allow user modifying the action file is intended to work; as that file will get overwritten on every update which changes remote actions file list.
But, I guess almost nobody would use this; so nobody would complain.
Otherwise, LGTM.
So take my approval.
e39bcb1 to
5c4674f
Compare
This provides a mechanism by which we can trigger remote actions using fioconfig and the new `run-and-report` command. In order to prevent the execution of random commands, we include a "actions" directory where a user can be explicit about which remote actions they want to allow for their product. This commit includes a "reboot" command that's been requested in the past. Signed-off-by: Andy Doan <andy@foundries.io>
Signed-off-by: Andy Doan <andy@foundries.io>
This change helps the user facing UX part of this feature. By sharing what actions are availble to the device, fioctl and webui can know what options to present to the user for triggering a remote action. It can also *reject* an invalid trigger rather than waiting for it to fail.
Signed-off-by: Andy Doan <andy@foundries.io>
5c4674f to
05418c5
Compare
This builds on the
run-and-reportchanges we've previously merged into fioconfig to create a mechanism for running remote actions.