cedar-go: remove vendor directory#87
Merged
patjakdev merged 1 commit intocedar-policy:mainfrom Apr 18, 2025
Merged
Conversation
Having a vendor directory for a library module like the SDK is of dubious value generally. Ultimately, the library will be consumed by an executable binary whose final set of dependencies will be determined by looking at all of its transitive library dependencies and our set of vendored dependencies will be ignored in that process. I did a survey of a few dozen of the most popular Go libraries and couldn't find another instance of an library module vendoring its dependencies. Signed-off-by: Patrick Jakubowski <patrick.jakubowski@strongdm.com>
patjakdev
force-pushed
the
remove-vendor-dir
branch
from
6837402 to
d9cafda
Compare
apg
approved these changes
Apr 18, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
Having a vendor directory for a library module like the SDK is of dubious value generally. Ultimately, the library will be consumed by an executable binary whose final set of dependencies will be determined by looking at all of its transitive library dependencies and our set of vendored dependencies will be ignored in that process.
I did a survey of a few dozen of the most popular Go libraries and couldn't find another instance of an library module vendoring its dependencies.