envoyproxy/envoy

Recording dependencies

Open

#23,928 opened on 2022年11月10日

GitHub で見る
 (1 comment) (0 reactions) (1 assignee)C++ (5,373 forks)batch import
area/docsdependenciesenhancementhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (平均マージ 8d) (30d で 378 merged PRs)

説明

Title: Record components used when Envoy was built

Description: From a software supply chain viewpoint it is desirable to record all dependencies used by a build of Envoy. As different configuration/compile time options include different dependencies, this information should be made available and installed with the Envoy binary. As the software dependencies contain different copyright and attribution requirements, these should also be recorded when recording the dependency information. Having dependency information available makes it possible to detect for example which Envoy instances need to be rebuilt and restarted if a bug is discovered in one of the dependencies, or to create verifiable builds. This information needs to be collected at build time, presumably collected by Bazel with attribution information extracted from the release tar balls of the dependencies.

Relevant Links: Some work in progress for Bazel license checking rules are at https://github.com/bazelbuild/rules_license that could be used as a base.

コントリビューターガイド