-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
argo: 2.2.1 -> 2.4.1 #70672
argo: 2.2.1 -> 2.4.1 #70672
Conversation
@GrahamcOfBorg build argo |
1 similar comment
@GrahamcOfBorg build argo |
you need to be whitelisted for ofborg to run your commands :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nix-review
passes on NixOS
diff LGTM
executable seems to work
[63 built, 2 copied (4.8 MiB), 0.7 MiB DL]
https://github.com/NixOS/nixpkgs/pull/70672
1 package were build:
argo
cc @kalbasit for go input
}; | ||
|
||
goDeps = ./deps.nix; | ||
goPackagePath = "github.com/argoproj/argo"; | ||
subPackages = [ "cmd/argo" ]; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why switch to installing only argo
? What about the other two commands?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can keep the other 2 binaries, but they are really only useful inside a Kubernetes Operator context when the full argo system is installed on a cluster.
The argo
CLI is what I think is more relevant to users. It's more like a argoctl
, but such a project does not exist.
I'm happy to add back the rest of the binaries if you prefer? Or I can add them back if somebody asks for them in the community?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm ok to leave them off. We can add them if someone asks for them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
another option would be to add a argoFull
where they are available. But if the closure saving is minimal I'm okay with them being added back.
@GrahamcOfBorg build argo |
(cherry picked from commit 5078eba)
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)Notify maintainers
cc @