Skip to content
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

Tanka init, set --jsonnetpkg-home #820

Open
ghostsquad opened this issue Mar 12, 2023 · 0 comments
Open

Tanka init, set --jsonnetpkg-home #820

ghostsquad opened this issue Mar 12, 2023 · 0 comments
Labels
kind/enhancement Improve something existing

Comments

@ghostsquad
Copy link

I'd like to be able to set the --jsonnetpkg-home for jsonnet-bundler, as the vendor directory conflicts with go vendoring, I want to use jsonnet-vendor instead.

ghostsquad added a commit to ghostsquad/currency-converter-practice that referenced this issue Mar 12, 2023
go and jsonnet/jb/tanka fight over the `vendor` directory. This is somewhat fixed with `-mod=readonly` or `-mod=mod` as an explicit flag to go commands, or `GOFLAGS=-mod=mod`, however, Jetbrains GOLAND still has problems if the `vendor` directory exists and doesn't have go files in it. See https://youtrack.jetbrains.com/issue/GO-10952/No-way-to-disable-vendoring-for-Sync-Dependencies-quick-fix. To get Goland to not freak out, `rm -rfd vendor`. This of course breaks all the Jsonnet, so when you are ready to do anything else, run `task jb:install`.

Another possible way to fix this is if tanka supported other vendor directories. See grafana/tanka#356 and grafana/tanka#820.
@zerok zerok added the kind/enhancement Improve something existing label May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improve something existing
Projects
Status: Backlog
Development

No branches or pull requests

2 participants