Way to handle state in NixOps4 #169

New issue

Closed

opened 2025-02-20 12:53:16 +01:00 by kiara · 2 comments

kiara commented

2025-02-20 12:53:16 +01:00

Owner

At present, our repo has a lot of hard-coded info that in practice should not be static global state, but rather state specific to a given deployment. A current examples of this is SSH keys.

Ideally, we would instead be able to handle such state through NixOps4, so that deployments would no longer depend on our source code, but SSH keys for example could rather be generated on the fly for subsequent updates to a deployment.

At present, our repo has a lot of hard-coded info that in practice should not be static global state, but rather state specific to a given deployment. A current examples of this is SSH keys. Ideally, we would instead be able to handle such state through NixOps4, so that deployments would no longer depend on our source code, but SSH keys for example could rather be generated on the fly for subsequent updates to a deployment.

kiara commented

2025-02-24 10:14:08 +01:00

Author

Owner

estimated at ~2w

kiara added a new dependency

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

#170 Way to handle task dependencies in NixOps4

kiara added a new dependency

2025-02-24 10:39:40 +01:00

#184 show indicator of actual deployment progress

kiara removed a dependency