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
I have tkn installed (actually compiled from source) that is not in my PATH it would be nice if I can be able to specify the tkn cli path instead of having the extension asking me every time to download it...
The text was updated successfully, but these errors were encountered:
The scenario here is the extension bundled with specific version of tkn allows to work with features specific to that release. If users try to run tkn from path, and if the version is very old, this can create compatibility issues for any features and can cause confusion to the workflow.
Yeah we can have a feature to ask user to provide the path of the installed binary (if extension does not detect it). Is there a version, upto what backward compatibility is supported?
Let's say we have latest tkn as v0.23.1, upto which versions of tkn would we support backward compatibility. This can help us to notify users in IDE if the path provided is very old.
I have tkn installed (actually compiled from source) that is not in my PATH it would be nice if I can be able to specify the tkn cli path instead of having the extension asking me every time to download it...
The text was updated successfully, but these errors were encountered: