-
Hi all, currently i have a few imports in use via jsonnet-bundler. These seem to be using subdirs instead of tags for versions. {
"version": 1,
"dependencies": [
{
"source": {
"git": {
"remote": "https://github.com/jsonnet-libs/cert-manager-libsonnet.git",
"subdir": "1.15"
}
},
"version": "main"
}
]
} I'd be interested if there is a better way without using the fixed version in jsonnet-code to import those than doing this:
and having to replace all occurences. How are you handling these? regards, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
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.
These are "legacy" import paths created by jsonnet-bundler. You can the creation of these symlinks by putting |
Beta Was this translation helpful? Give feedback.
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.
These are "legacy" import paths …