Skip to content

Redo dependency system #314

Description

@viccuad

Provide a new implementation for a dependency system.
Ideally, it would look similar or if not the same to https://github.com/cloudfoundry-incubator/kubecf/tree/master/scripts/tools.

Some constraints that have popped up:

  • Needs to be flat. No utilities should be pre-depended on before others (eg: current catapult depends on jq to be able to craft configs, that may be used later on to obtain yq).
  • Obtained dependencies must be stored in a way so they are cacheable (by CI, etc). Bonus points if they don't get redownloaded every time one creates a new build dir for a cluster.
  • Needs to support several versions of binaries. E.g: kubectl versions. These versions will get used on the test environment, depending on the cluster k8s version.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions