Add support for Fioconfig by doanac · Pull Request #109 · foundriesio/fioup

doanac · 2025-10-24T03:08:01Z

This series of changes introduces support for fioconfig in the following ways:

fioup daemon will now check config during each interval
fioup config-check can be run by hand
fioup run-and-report can be used exactly like the version in fioconfig

doanac · 2025-10-24T03:17:54Z

This is missing documentation, but I want y'all to give feedback before we try and do that. I think docs can be a separate PR.

doanac · 2025-10-24T03:18:02Z

This is missing a couple things, but I wanted y'all to see what I have. Things missing:

a systemd service to extract secrets earlier in the boot
documentation

mike-sul · 2025-10-28T11:06:45Z

@doanac Maybe it makes sense to move the first 3 commits into the separate PR?

doanac · 2025-10-28T13:42:27Z

Maybe it makes sense to move the first 3 commits into the separate PR?

totally. I'd been thinking about doing this in an attempt to make this less noisy. But as 3 different PRs. I'll start splitting them now.

doanac · 2025-10-30T18:20:52Z

@mike-sul @detsch - this is a new approach based on all the daemon refactor work. I'm hitting a small thing with app switching that Mike seems to know how to fix. However, the logging appears to show its doing the right things with config-reload logic.

This works just like the `fioconfig check-in` command Signed-off-by: Andy Doan <andy@foundries.io>

This allows secrets to be extracted earlier in the boot for services that may need them before fioup daemon is up and running. Signed-off-by: Andy Doan <andy@foundries.io>

This mimicks the same handy feature included in fioconfig. Signed-off-by: Andy Doan <andy@foundries.io>

Signed-off-by: Andy Doan <andy@foundries.io>

This uses the same naming as the LmP so that fioctl and the WebUI will work the same way regardless of the OTA client. Signed-off-by: Andy Doan <andy@foundries.io>

If the command is run with a TTY, we'll assume the user is running commands from the CLI and wants a more basic output. If no TTY is present, we'll assume a daemon mode from a service where structured logging would be preferred. Example with TTY: ``` $ fioup check ERROR: Unable to run lshw: error=exec: no command 2 [intel-corei7-64-lmp-2] 3 [intel-corei7-64-lmp-3] 8 [intel-corei7-64-lmp-8-debian-sway] telegraf-agent hub.foundries.io/andy-debian-sway/telegraf-agent@sha256:f35401dbe539037b9a624bf74f5f3200b3fd2b2f86f922009720f2a82ac87cca Current version: intel-corei7-64-lmp-8-debian-sway You are running the latest version. $ fioup daemon Daemon starting: pid=276378 ERROR: Unable to run lshw: error=exec: no command Extracting file: file=z-50-fioctl.toml Extracting file: file=fioconfig-oneshot-diag Extracting file: file=fioup-test Extracting file: file=foo Config on server has not changed [1/5] Checking:ERROR: Error during update: error=failed at state Checking: latest target installation attempts has reached the limit (3) Waiting before next check...: interval=1m0s ``` Example with no TTY: ``` $ fioup check 2>&1 | tee /dev/null time=2025-10-23T21:59:46.963-05:00 level=ERROR msg="Unable to run lshw" error="exec: no command" 2 [intel-corei7-64-lmp-2] 3 [intel-corei7-64-lmp-3] 8 [intel-corei7-64-lmp-8-debian-sway] telegraf-agent hub.foundries.io/andy-debian-sway/telegraf-agent@sha256:f35401dbe539037b9a624bf74f5f3200b3fd2b2f86f922009720f2a82ac87cca Current version: intel-corei7-64-lmp-8-debian-sway You are running the latest version. $ fioup daemon 2>&1 | tee /dev/null time=2025-10-23T22:03:52.462-05:00 level=INFO msg="Daemon starting" pid=276395 time=2025-10-23T22:03:52.462-05:00 level=ERROR msg="Unable to run lshw" error="exec: no command" time=2025-10-23T22:03:52.463-05:00 level=INFO msg="Extracting file" file=z-50-fioctl.toml time=2025-10-23T22:03:52.463-05:00 level=INFO msg="Extracting file" file=fioconfig-oneshot-diag time=2025-10-23T22:03:52.463-05:00 level=INFO msg="Extracting file" file=fioup-test time=2025-10-23T22:03:52.463-05:00 level=INFO msg="Extracting file" file=foo time=2025-10-23T22:03:52.687-05:00 level=INFO msg="Config on server has not changed" [1/5] Checking:time=2025-10-23T22:03:52.949-05:00 level=ERROR msg="Error during update" error="failed at state Checking: latest target installation attempts has reached the limit (3)" time=2025-10-23T22:03:52.949-05:00 level=INFO msg="Waiting before next check..." interval=1m0s ``` Signed-off-by: Andy Doan <andy@foundries.io>

Before using fioconfig operations, we need to ensure we have permission to extract files into the secrets directory. This command will produce an error like: ``` $ ./bin/fioup config-extract ERROR: Unable to create files in `secrets-dir`: open /run/secrets/.test-writeable: permission denied ``` Signed-off-by: Andy Doan <andy@foundries.io>

doanac · 2025-10-31T16:04:38Z

rebased on latest main.

doanac requested review from detsch and mike-sul October 24, 2025 03:08

doanac force-pushed the fioconfig-support branch from bc8f8f2 to a64cd58 Compare October 24, 2025 03:39

mike-sul reviewed Oct 24, 2025

View reviewed changes

Comment thread cmd/fioup/daemon.go Outdated

This was referenced Oct 24, 2025

Add fioconfig functionality to allow configuring app list remotely #86

Closed

Add ability to change a tag and execute commands remotely (fioconfig) #87

Closed

mike-sul reviewed Oct 24, 2025

View reviewed changes

Comment thread cmd/fioup/daemon.go Outdated

doanac force-pushed the fioconfig-support branch from a64cd58 to 25cba14 Compare October 27, 2025 20:24

mike-sul reviewed Oct 27, 2025

View reviewed changes

Comment thread cmd/fioup/daemon.go Outdated

mike-sul reviewed Oct 28, 2025

View reviewed changes

Comment thread internal/register/docker.go

mike-sul reviewed Oct 28, 2025

View reviewed changes

Comment thread cmd/fioup/daemon.go Outdated

doanac force-pushed the fioconfig-support branch from 25cba14 to 6364065 Compare October 30, 2025 18:18