init diskLayouts #302
No reviewers
Labels
No Label
backups
blog
bootstrapping
bug
changes-requested
cli
documentation
duplicate
enhancement
facts
help wanted
invalid
Inventory
low_prio
manager
modules
needs-review
networking
packaging
question
secrets
template
test
tooling
user-testing
vm
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: clan/clan-core#302
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "lassulus-HEAD"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
add clan_core path helper function
pytest: add impure marker
cli: rename admin create to create
init clanModules.diskLayouts
secrets sops: deploy age key
58257c9284
to5f3061fcef
use experimental flags everywhereto init diskLayouts5f3061fcef
to201acc9614
fcc98a18cb
to2b08f233fa
2b08f233fa
to3a8b9fc9b6
3a8b9fc9b6
to218451e79f
8680cbaf4e
tob3159559f4
b3159559f4
to3b5f532fe4
3b5f532fe4
toe51f3b6a14
e51f3b6a14
to359f776e6d
ec35f8085c
to5f7a925322
@ -71,0 +33,4 @@
generateSecrets = pkgs.writeScript "generate-secrets" ''
#!${pkgs'.python3}/bin/python
import json
from clan_cli.secrets.generate import generate_secrets_from_nix
how is clan_cli made available here? it would be nicer to have this independent of the clan_cli package.
We depend on the clan cli already because this is used to set secrets. So we would first need to make the secrets cli independent of clan.
5f7a925322
to9363dec49f
@ -71,0 +34,4 @@
#!${pkgs'.python3}/bin/python
import json
from clan_cli.secrets.generate import generate_secrets_from_nix
args = json.loads(${builtins.toJSON (builtins.toJSON { machine_name = config.clanCore.machineName; secret_submodules = config.clanCore.secrets; })})
doesn't this also need 2 json.loads? otherwise it's just one big string?
No. it's a python string that gets parsed as json.
@ -0,0 +1,44 @@
{ config, lib, ... }:
This pull requests already touches a lot of stuff. Can you split the disko part into a new pull request?
I think disk partition configurations needs to be versioned so we can evolve the format without breaking existing machines.
f29dcc0a70
to15a578b455
15a578b455
toad15d9a6c7
ad15d9a6c7
to456b3c9769
456b3c9769
to3923feb66e
3923feb66e
toac37453258
ac37453258
toa522ee2611
a522ee2611
to8bdc780eee
8bdc780eee
to67c79f411d
67c79f411d
tod983a77fb9
d983a77fb9
toc91d7d8c2e
c91d7d8c2e
to62ad4bcd67