add module to generate zerotier configuration #22
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: clan/clan-core#22
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "zerotier"
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?
@ -0,0 +90,4 @@
controller_port = find_free_port(range(10000, 65535))
zerotier_exe = shutil.which("zerotier-one")
if zerotier_exe is None:
raise Exception("cannot find zerotier-one executable")
@DavHau I am already not a fan of 100% test coverage. It does not seem practical to setup tests for every error path. It would just result in a slow and harder to maintain test suite that test things that don't matter.
OK, my intention was not to enforce actual 100% coverage. More like making it an explicit decision to not cover something, by having to put a
pragma: no cover
comment somewhere.We can remove the coverage enforcement, but then the coverage will most likely converge towards 0%, don't you think so?
Via #21 I also now added the html coverage output by default.
If you keep your browser open, then it should be simple to find the lines to exclude quickly.
9ca0f585d4
to27d376fe1f
27d376fe1f
to8ae99ac9d7
8ae99ac9d7
to5ec203681f
@ -0,0 +86,4 @@
# This check could be racy but it's unlikely in practice
controller_port = find_free_port(range(10000, 65535))
zerotier_exe = shutil.which("zerotier-one")
if zerotier_exe is None:
why not use nix shell here? we did that in the clan ssh command, and it seems like a cool way
Would this not quite hard to test in a nix-build?
We can build a python function which would check if its installed (then we can supply the packages in a test) or get it when it's not there?
Problem is though that we might get a binary that is not build with nix and that behaves differently. How would you check that we only get the binary that we provided ourself? Someone could for example do nix-shell -p bubblewrap and than run our tool.
But that is fine and we get a fast cli
Also the python function can check if the file begins with /nix/store
done.
@ -0,0 +99,4 @@
home = tempdir / "zerotier-one"
home.mkdir()
cmd = [
"bwrap",
same here, I guess we can hardcode some dependencies, but only if we need them in more than 1 codepath?
e1c388136c
to98593fc284
98593fc284
tocfd7db6388
cfd7db6388
to729a2837e7
4215a28dd2
tob9c2a131bc
b9c2a131bc
to821ff71e4a