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
When we install a mixin, we need to remember where it came from so that we can upgrade it later without having to specify again where to get the new binaries.
Porter should save this to a new file located at PORTER_HOME/mixins/cache.json.
When we install a mixin, we need to remember where it came from so that we can upgrade it later without having to specify again where to get the new binaries.
Porter should save this to a new file located at PORTER_HOME/mixins/cache.json.
feedURL
andurl
correspond to the original flags passed toporter mixin install
, which can be either--feedURL
or--url
.I suggest looking at implementing this functionality in this area:
https://github.com/deislabs/porter/blob/b24cdd412147c8156942f6d8accb489e71e48e6f/pkg/mixin/provider/install.go#L17-L23
It has a reference to a
Config
struct which has useful methods likegetMixinsDir()
which you will need in order to figure out where to write the file.You can test this out by building and installing porter, then running
porter mixin install exec
. Then check the file in ~/.porter/mixins/cache.json.The text was updated successfully, but these errors were encountered: