Way to handle task dependencies in NixOps4 #170

New issue

Closed

opened 2025-02-20 12:58:13 +01:00 by kiara · 1 comment

kiara commented

2025-02-20 12:58:13 +01:00

Owner

As part of our deployment, some tasks will depend on others part of the deployment. An example of this is NixOS deployments depending on the provisioning of a VM, where we should ensure that:

deployment of the desired configuration would only be triggered after provisioning of a VM finishes;
relevant information dependencies between tasks are properly handled without hard-coding, e.g. passing IP addresses of provisioned VMs to the deployment task, so that it knows which machine should be accessed.

As part of our deployment, some tasks will depend on others part of the deployment. An example of this is NixOS deployments depending on the provisioning of a VM, where we should ensure that: 1. deployment of the desired configuration would only be triggered after provisioning of a VM finishes; 1. relevant information dependencies between tasks are properly handled without hard-coding, e.g. passing IP addresses of provisioned VMs to the deployment task, so that it knows which machine should be accessed.

kiara added a new dependency

2025-02-24 10:15:51 +01:00

#169 Way to handle state in NixOps4

kiara added the

component: nixops4

label

2025-03-03 08:15:22 +01:00

kiara added a new dependency

2025-04-02 08:52:00 +02:00

#296 orchestrator features

kiara commented

2025-04-14 11:08:23 +02:00