You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@Duologic the article you linked is more or less what I have already put in place.
Anyway there are cases where the data cannot be just put statically in a file, or should I say that it's less convenient to do that.
Think about CI environments for example.
I know that it's possible to circumvent this in different ways (exporting env vars into files is one on them) but I think it would be much easier if one could use tk export or tk env list without rethinking everything in term of static imports without tla .
After all, the code I put above is a perfectly valid jsonnet, isn't it?
I have the following jsonnet to produce inline environments:
With this setup it's not possible to use
tk export
to export the generated yaml, I think because as reported heretk env
doesn't work either.Also, I don't see another way to pass the
apiServer
dinamically as top level arg, becausetk set
doesn't work with inline environment.The only workaround I found is to rely on
tk show --dangerous-allow-redirect
piped intokubectl
which is obviously not recommended.The text was updated successfully, but these errors were encountered: