Dep Cloud Native Buildpack

The Dep CNB provides the dep executable. The buildpack installs dep onto the $PATH which makes it available for subsequent buildpacks and/or the final container image.

Integration

The Dep CNB provides dep as a dependency. Downstream buildpacks can require the dep dependency by generating a Build Plan TOML file that looks like the following:

[[requires]]

  # The name of the Dep dependency is "dep". This value is
  # considered part of the public API for the buildpack and will not change
  # without a plan for deprecation.
  name = "dep"

  # Note: The version field is unsupported as there is no version for a set of
  # dep.

  # The Dep buildpack supports some non-required metadata options.
  [requires.metadata]

    # Setting the build flag to true will ensure that the Dep
    # dependency is available on the $PATH for subsequent buildpacks during
    # their build phase. If you are writing a buildpack that needs to run Dep
    # during its build process, this flag should be set to true.
    build = true

    # Setting the launch flag to true will ensure that the Dep
    # dependency is available on the $PATH for the running application. If you are
    # writing an application that needs to run Dep at runtime, this flag should
    # be set to true.
    launch = true

Usage

To package this buildpack for consumption:

$ ./scripts/package.sh

This builds the buildpack's Go source using GOOS=linux by default. You can supply another value as the first argument to package.sh.

buildpack.yml Configuration

The dep buildpack does not support configurations via buildpack.yml.