enqueuing deployment syncs

kiara commented

2025-03-12 13:32:37 +01:00

Owner

As a user of a Fediversity web front-end,
I want to be able to enqueue distinct configuration deployment syncs,
so that my UI could focus on a single application at a time.

implementation notes

this comes down to using a queue, potentially backed by multiple builders (#366)
- ideally dropping outdated syncs for a deployment in favor of the newer one
nix-specific builder queues seem an open challenge still, with underlying work including work on the nix protocol

**As** a user of a Fediversity web front-end, **I want** to be able to enqueue distinct configuration deployment syncs, **so that** my UI could focus on a single application at a time. ### implementation notes - this comes down to using a queue, potentially backed by multiple builders (#366) - ideally dropping outdated syncs for a deployment in favor of the newer one - nix-specific builder queues seem an open challenge still, with underlying work including work on the [nix protocol](https://www.tweag.io/blog/2024-04-25-nix-protocol-in-rust/)

fricklerhandwerk commented

2025-03-14 11:50:03 +01:00

Owner

What's a "sync"?

kiara commented

2025-03-14 12:21:07 +01:00

Author

Owner

@fricklerhandwerk currently our button i think said deploy, but that's a bit of a misnomer, given pressing it instead syncs configuration, which may simply alter settings for an existing service.

fricklerhandwerk commented

2025-03-17 09:16:44 +01:00

Owner

Ah so you're saying that what we today call deployment should be async? Yes, it should be that in any case, and it's implied in the later user stories where one gets a notification once a deployment is done, even when leaving the page early.

kiara commented

2025-03-17 12:26:15 +01:00

Author

Owner

not just async. this story came from the recent meeting with the designers, who envisioned services to be separated across UI sections, each of which presumably altered independently. following such a UI, it would make sense for a deployment system to support that, e.g.:

edit mastodon config
edit pixelfed config
start editing peertube config
receive notification mastodon sync succeeded
finish editing peertube config
receive notification pixelfed sync succeeded
receive notification peertube sync succeeded

not just async. this story came from the recent meeting with the designers, who envisioned services to be separated across UI sections, each of which presumably altered independently. following such a UI, it would make sense for a deployment system to support that, e.g.: 1. edit mastodon config 1. edit pixelfed config 1. start editing peertube config 1. receive notification mastodon sync succeeded 1. finish editing peertube config 1. receive notification pixelfed sync succeeded 1. receive notification peertube sync succeeded

👍 1

kiara commented

2025-03-23 09:34:29 +01:00

Author

Owner

c.f. https://opentofu.org/docs/cli/commands/plan/#resource-targeting