getporter / magefiles Goto Github PK

Right now we have a mage target that installs porter:

https://github.com/getporter/porter/blob/ebf411829f8f70d962486fd09e08a840c132f633/mage/tools/install.go#L95

But it grabs the "latest" version, which is a v0.38.* release. It would be great to have a target, like EnsurePorterAt(version string) that let's you get a specific version of porter so that mixins and plugins that install porter for testing can pick a prerelease version instead.

Let's add some common functions to get plugins and mixins.

Originally posted by @carolynvs in getporter/operator#98 (comment)

Now that magex supports installing into a local directory (for direct downloads, not installing from the go package), we can start installing necessary tools into a local directory, like bin/ or tools/. That will give us more control over how the tools are resolved, and which version we want to use without altering anyone's system.

Instead of having each mixin/plugin add a workaround to the apple silicon copy bug, we could add a helper function like ReplaceBinary/Dir that runs a rm before doing a copy.

See getporter/porter#2543

I think it would be useful to compile and publish versioned tags of these targets so they can be ran directly from the binary without needing to have a local go file to run mage from. Ran into this use case when playing around with kind clusters in a different project that didn't have any go code in it and all that was needed was a reliable way to create a kind cluster.

Ex:

curl https://api.github.com/<repo/artifact...> -o mageutils

./mageutils EnsureTestCluster (or any other useful target)

Something like that...

Using XBuildAll to build a plugin tries to publish to a mixin directory structure.

Should thePlublishMixinForPublish be relocated to the mixins package or perhaps a plugins package?

Current kind is at v0.12.0 and will create clusters at v1.23. Updating kind to v0.20.0 will create clusters at v1.27.3