Generalize goal of deployments #4

Open
opened 2024-05-24 20:29:44 +02:00 by rlahfa · 1 comment
Owner
Possible values:
          - build:        Build the configurations only
          - push:         Push the closures only
          - switch:       Make the configuration the boot default and activate now
          - boot:         Make the configuration the boot default
          - test:         Activate the configuration, but don't make it the boot default
          - dry-activate: Show what would be done if this configuration were activated
          - upload-keys:  Only upload keys
  • build: we can generalize by explaining what is the attribute name to build
  • push: we can generalize by explaining how to copy-closure to target
  • switch: we can generalize by explaining how to activate an "toplevel"-like item with a target configuration
  • boot: worst case, it's a nop, best case, we just write a configuration for next reboot, i.e. push closures, write the new userspace, do not reload s6 services (for Liminix)
  • test: impossible to support currently on Liminix.
  • dry-activate: we can explain what script to call.
  • upload-keys: signal support or not in the registry.
``` Possible values: - build: Build the configurations only - push: Push the closures only - switch: Make the configuration the boot default and activate now - boot: Make the configuration the boot default - test: Activate the configuration, but don't make it the boot default - dry-activate: Show what would be done if this configuration were activated - upload-keys: Only upload keys ``` - build: we can generalize by explaining what is the attribute name to build - push: we can generalize by explaining how to copy-closure to target - switch: we can generalize by explaining how to activate an "toplevel"-like item with a target configuration - boot: worst case, it's a nop, best case, we just write a configuration for next reboot, i.e. push closures, write the new userspace, do not reload s6 services (for Liminix) - test: impossible to support currently on Liminix. - dry-activate: we can explain what script to call. - upload-keys: signal support or not in the registry.
Author
Owner
  1. Go through all TODOs and generalize appropriately.
  2. #5
  3. #6
  4. #7
1. Go through all `TODOs` and generalize appropriately. 2. https://git.dgnum.eu/DGNum/colmena/issues/5 3. https://git.dgnum.eu/DGNum/colmena/issues/6 4. https://git.dgnum.eu/DGNum/colmena/issues/7
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: DGNum/colmena#4
No description provided.