Skip to content

Properly versioning external tool dependencies #15909

Open
@neuronull

Description

@neuronull

Currently we rely on some external tooling some aspects of development.
One such example is cue.

These external tools often get updated, and sometimes those updates break compatability with prior versions.
Developers are left to maintain their local workspaces to the same versions that CI is running.
This is also painful for the larger body of community contibutors. (See #15696 (comment) )

We have make environment but, it would nice if we had something more robust.

One small option to start, is we could have version checks for tools like cue, at the top of the cue scripts. To make sure the user's version meets the requirements of vector.

Other options include nix or tools built on top of nix, like https://github.com/DeterminateSystems/riff .

We should explore these options and make selection to improve the development experience.

Metadata

Metadata

Assignees

No one assigned

    Labels

    domain: depsAnything related to Vector's dependenciesdomain: setupAnything related to setting up or installing Vectormeta: ideaAnything in the idea phase. Needs further discussion and consensus before work can begin.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions