-
Notifications
You must be signed in to change notification settings - Fork 11
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
Fix and document go install
method of installation
#718
Comments
Looks like we evaluated this in #583 (comment) and it can't be done because these build args are required? BUILD_ARGS := -s -w -X 'github.com/defenseunicorns/uds-cli/src/config.CLIVersion=$(CLI_VERSION)' \
-X 'github.com/defenseunicorns/zarf/src/config.ActionsCommandZarfPrefix=zarf'
Is that all? Surely we could default |
Does
|
That build arg forces bundled Zarf packages that use Zarf Actions to use the vendored |
Noting too that we use many build args (as does Zarf) |
Appreciate the issue @marshall007 ! Given the complexity of removing the build args, I'd like to better understand the use case for doing |
^ also if I'm missing something and we can do |
If installing from |
@UncleGedd I'm on Linux. I could use
All of these build args you've linked to are seemingly only used for our own wrapper around I think we could get the same (or better) information using the |
Great points. This issue will be tough for the team to prioritize in the coming weeks, but we'd happily welcome a PR if you're interested |
Thanks, I will assign myself and try to get around to it this week. |
Ok it's a bit of a mixed bag, but I think all the variables that are actually functional/load-bearing can be set at runtime.
|
Environment
Device and OS: Linux
App version:
>= v0.11.1
Steps to reproduce
go install github.com/defenseunicorns/uds-cli@v0.11.0
worksgo install github.com/defenseunicorns/uds-cli@latest
does notAdditionally, it would be great if we created a module named
cmd/uds
so thatgo install github.com/defenseunicorns/uds-cli/cmd/uds@latest
creates a binary nameduds
instead ofuds-cli
. Alternatively, we could detect of the binary name when calling the CLI program so that calling./uds
in tasks is rewritten to the correct path place no matter what the host binary is named.Visual Proof (screenshots, videos, text, etc)
Additional Context
The
replace
directives added in #662 (seego.mod#L530-L535
) prevent this method of installation.The text was updated successfully, but these errors were encountered: