Skip to content

Handling of versioned jsonnet imports? #1228

Answered by zerok
strowi asked this question in Q&A

You must be logged in to vote

I doubt that there is a way to avoid hardcoding these somewhere since jsonnet does not support dynamic imports. What you can do, though, is collect all these into a single library and import the dependencies from there. This way you only have two places that need to be updated eventually instead of 1+n 🙂

I think the best way to solve something like this would be through an extension of jsonnet-bundler to allow it to write to an arbitrary vendor folder. Haven't found a relevant ticket for that yet, though.

And i also saw symlinks created in vendor/$version - what's the point of these? And what happens if i have 2 different vendors having the same version?

These are "legacy" import paths …

Replies: 1 comment 1 reply

You must be logged in to vote
1 reply
@strowi

Answer selected by strowi
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants