-
Notifications
You must be signed in to change notification settings - Fork 16
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
feat(config): make it so you can revert override of apps #440
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
@@ -26,7 +26,16 @@ currently configured and reporting.`, | |||||||||
|
||||||||||
# Set the docker apps and the tag: | ||||||||||
fioctl devices config updates <device> --apps shellhttpd --tag master | ||||||||||
`, | ||||||||||
|
||||||||||
# Set the docker apps to none, meaning it will run no apps: | ||||||||||
fioctl devices config updates <device> --apps , | ||||||||||
|
||||||||||
# Set the docker apps to inherit from their parent, meaning: | ||||||||||
# If for a device apps are not set - all apps are installed | ||||||||||
# If for a device apps are set* - only those apps are installed | ||||||||||
# | ||||||||||
# * It can be set at the individual device level, or at a device group level | ||||||||||
fioctl devices config updates <device> --apps -`, | ||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. explain what "parent" and "none" mean here also There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would state explicitly here that we are inheriting from the group config.
Suggested change
We might be more verbose (like below), but I think that is apparent from the
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Once I wrote this I understood we don't yet have a way to restore the device tag to inherit from a group config or system default. @doanac @mike-scott ^^^ There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. probably should do it also |
||||||||||
} | ||||||||||
configCmd.AddCommand(configUpdatesCmd) | ||||||||||
configUpdatesCmd.Flags().StringP("tag", "", "", "Target tag for device to follow") | ||||||||||
|
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.
We still aren't explain what the "parent" will be. I'm not sure parent is a good word. What we are trying to describe is how are config files are processed. We use the same logic as systemd where we walk through:
We need a concise way to explain this.
And that
,
and-
are so subtle here that we should probably call out that they are special characters.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.
IIUC the group level is the top one here (as we allow no factory-wide updates config).
So, probably, we may put here a sentence like this:
A system default seems to be rather specific to me, without diving into internal details (which can differ from device to device).