settings: Expose GIT_OPT_SET_OWNER_VALIDATION option #971
Conversation
This file contains 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
By default, `libgit2` will throw an error if you try to open a repository not owned by the current user. An option to disable this validation is available, but wasn't being exposed in `rugged`. This commit exposes fetching and setting this option via a new `owner_validation` setting. (My use case is using `rugged` in a ruby language AWS lambda function connected to EFS. In this scenario, the EFS access point is configured with a POSIX user ID and group ID `used for all file system operations using this access point`, but the lambda's execution environment's uid is not known upfront and won't match).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
By default,
libgit2will throw an error if you try to open a repository not owned by the current user. An option to disable this validation is available, but wasn't being exposed inrugged.This commit exposes fetching and setting this option via a new
owner_validationsetting.(My use case is using
ruggedin a ruby language AWS lambda function connected to EFS. In this scenario, the EFS access point is configured with a POSIX user ID and group IDused for all file system operations using this access point, but the lambda's execution environment's uid is not known upfront and won't match).