Skip to content

Latest commit

 

History

History
112 lines (69 loc) · 9.48 KB

0060-dependency-mirrors.md

File metadata and controls

112 lines (69 loc) · 9.48 KB
Raw

Easy Dependency Mirrors

Summary

Presently, you can either take the dependencies shipped with a Paketo buildpack or you can create a whole bunch of dependency mapping bindings to change each dependency you want to override individually. There is no option to override all dependencys and point them to a mirror that is convenient.

Motivation

  1. Managing lots of dependency bindings is tedious and a frequent pain point, so much so that there are now tools to help generate and manage these.

  2. Managing lots of dependency bindings does not scale because you need to keep them up-to-date, but you can't easily know when new dependencies are updated. You also need to specify them per-application. There's no way to override this at a broader scale.

  3. For operations teams, this is particularly difficult because networks may not allow access to external repositories. This forces them to either build sets of custom buildpacks with different dependency data, or manage lots of binding files.

Detailed Explanation

This RFC proposes a standard interface that would allow a user to specify a mirror repository from which buildpacks can easily, and safely download dependencies.

When a user wants to use a dependency mirror, the user can signal that to Paketo buildpacks in two ways:

  1. Set the BP_DEPENDENCY_MIRROR environment variable where the value is the mirror URI.
  2. Include a binding with a type of dependency-mirror. The binding has key of default and a value that is the mirror URI.

The environment variable is more convenient but we need to support bindings as well because some repositories may require basic authentication credentials in the URLs (i.e. URL includes secrets). If both happen to be defined, then the environment variable takes precedent.

The format of the URI is: <scheme>://[<username>:<password>@]<hostname>[:<port>][/<prefix>]

  • The URL can have either a scheme of https:// or file://. We specifically will not allow http:// because this could introduce a way for a downgrade attack (i.e. someone tricks the user to downgrade from https to http).
  • If a path is specified on the URL, it prefixes the original path of the dependency. This is necessary in some cases where a mirror is hosting many different repositories.
  • The prefix path may include a place holder of {originalHost} which is substituted for the original host value. Again, this is to support mirrors that host many different repositories, which in some cases include the original hostname in the path.

When a mirror is specified the buildpack will take the data from the URL and use that to override parts of the original URL.

  • The mirror scheme overrides the original scheme
  • The mirror user/password overrides the original user/password
  • The mirror host overrides the original host
  • As mentioned above, the path from the mirror is prefixed onto the original URL path

For example, a mirror URL of https://user:[email protected]/buildpacks-dependencies/{originalHost} would translate to look up resources as follows:

  • The dependency URL of https://download.bell-sw.com/vm/22.3.5/bellsoft-liberica-vm-core-openjdk11.0.22+12-22.3.5+1-linux-amd64.tar.gz would be translated to https://user:[email protected]/buildpacks-dependencies/download.bell-sw.com/vm/22.3.5/bellsoft-liberica-vm-core-openjdk11.0.22+12-22.3.5+1-linux-amd64.tar.gz.
  • The dependency URL of https://github.com/watchexec/watchexec/releases/download/v1.25.1/watchexec-1.25.1-x86_64-unknown-linux-musl.tar.xz would be translated to https://user:[email protected]/buildpacks-dependencies/github.com/watchexec/watchexec/releases/download/v1.25.1/watchexec-1.25.1-x86_64-unknown-linux-musl.tar.xz.

Hostname Mapping

We expect most mirrors to be compatible with the above configuration options, however, if more control is required then you may set specific mappings on a per-hostname basis.

To do this, you may set any number of additional environment variables in the format BP_DEPENDENCY_MIRROR_<hostname>=https://mirror.example.com/... to define a mirror location specific to that hostname. The <hostname> part should be the hostname to match written in all upper case characters, with dots (i.e. .) replaced with a single underscore character (i.e. _) and dashes replaced with two underscore characters (i.e. __). For example, github.com is BP_DEPENDENCY_MIRROR_GITHUB_COM and examp-le.com is BP_DEPENDENCY_MIRROR_EXAMP__LE_COM.

When the buildpacks check for a host-specific dependency mirror, they will translate the target hostname by converting - to __ and . to _ and uppercasing the hostname. This is sufficient to cover all hostnames because hostnames are only allowed to have letters, numbers, and dashes with dots to separate each segment of the hostname.

You may optionally set a default mirror as well. Set BP_DEPENDENCY_MIRROR to the default mirror location. This location is used whenever a dependency needs to be fetched and there is not a specific mapping for that hostname. If no default mirror is set then the buildpack will download from the original location in its metadata.

Where this might be useful is if you have multiple mirror hosts or if you have a mirror host with a directory structure that does not follow the target hostname. You may then supply individual mappings to point each hostname to a specific mirror location.

For example:

BP_DEPENDENCY_MIRROR              https://mirror.example.org/{originalHost}
BP_DEPENDENCY_MIRROR_GITHUB_COM   https://mirror.example.org/public-github
BP_DEPENDENCY_MIRROR_NODEJS_ORG   https://mirror.example.org/node-dist

In this example, the buildpack will download dependencies from github.com through https://mirror.example.org/public-github. It will download dependencies from nodejs.org through https://mirror.example.org/node-dist. Everything else will be downloaded through https://mirror.example.org/{originalHost} and if not present on that mirror then downloads will fail.

BP_DEPENDENCY_MIRROR_GITHUB_COM   https://mirror.example.org/public-github
BP_DEPENDENCY_MIRROR_NODEJS_ORG   https://mirror.example.org/node-dist

If we use the above configuration, which is the same but does not have a default mirror then the buildpack will download dependencies from github.com through https://mirror.example.org/public-github. It will download dependencies from nodejs.org through https://mirror.example.org/node-dist. Everything else will be downloaded through the original URLs in the buildpack's metadata.

The same hostname mappings can be specified using a binding, and when using this method you do not need to do any hostname translation.

For the default mirror, the key is default and the value is the mirror URL. The default is not required when using bindings either. For hostname-specific mappings, you set the hostname to the binding key and the dependency mirror URL to the binding value.

For example:

/platform
    └── bindings
        └── dependency-mirror
            ├── default                https://mirror.example.org/{originalHost}
            ├── github.com             https://mirror.example.org/public-github
            ├── nodejs.org             https://mirror.example.org/node-dist
            └── type                   dependency-mirror

Rationale and Alternatives

  • You can clone a buildpack, modify buildpack.toml, then repackage it. Repeat this for every buildpack you need. Repeat it every time we release a new buildpack.
  • You can clone a buildpack and then repackage it in offline mode. This downloads the dependencies and bundles them within the image. Repeat this for every buildpack you need. Repeat it every time we release a new buildpack. Plus image sizes become gigantic, multiple GB.
  • You can generate a lot of dependency mapping bindings. This can work OK in small situations, but doesn't scale well in large orgs and teams. It is also difficult to keep up with over time as buildpacks update and include new dependencies.
  • You can install dependencies through some other means, like preinstall them onto the build/run images.

Implementation

Most of this is covered in the detailed explanation above, but breaking it down a bit more concretely.

We need to update both libpak and packit, both of which implement dependency downloads. The logic for both should be similar as they are both written in Go. The libpak implementation has already been done as an initial discussion and reference implementation.

That should be it. Individual buildpacks don't need to change beyond updating to a version of libpak or packit that includes the implementation of this RFC.

Prior Art

The Cloud Foundry Java Buildpack has similar mechanisms that allow a user to override the location from which it fetches dependencies. This allows users to mirror dependencies on network. It has some additional functionality that's not being proposed here, which is the ability to actually change what dependencies are included.

The proposal here would require a user to make a full mirror of the official dependency set and host that. You could, in theory, host a subset of the mirror, but there is nothing that would stop the buildpack from attempting to download dependencies that you've not mirrored. In that case, the build would fail with a download error. That use case is out of scope for this RFC.

Unresolved Questions and Bikeshedding

None