56quarters / tunic Goto Github PK

There should be an installer that supports placing a single (local) build artifact in a release directory. This would be useful for installing a Java jar or Python package with a main.py file.

This installer should accept a URL from which to download an artifact and then install it on a remote machine (similar to how LocalArtifactInstallation works).

Probably time to finally upgrade to Fabric 2 and start supporting Python 3. We should bump our version to 2 as part of this.

Older version of Fabric didn't have the warn_only context manager. Tunic should gracefully handle this case (it's a pretty simple definition when it's missing).

Settings to retry downloads are useful but they're currently buried several layers away from how people interact with HttpArtifactInstallation. No one wants to inject a bunch of esoteric functions to get retry logic. These settings should just be exposed in the constructor.

Once #2 is complete, create a wrapper that accepts a path, http(s) URL, or SSH hostname/path and delegates to the appropriate code. Introduce this in pre v2 and update docs to recommend that people just use this instead of the more specific classes.

After #3, the next way to make installers more flexible and easy to use is to let people apply some sort of 'unzip' to the artifact. This would help for legacy applications at ST that are 'built' by creating a tarball. It would also be useful for deploying WARs.