Custom header for dvc webdav (#8933)Fix https://github.com/iterative/dvc/issues/8931 #8933
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.
@skshetry I created a PR for the issue iterative/dvc-webdav#19 (by @conrad-stork) in order to add the possibility of setting a custom auth header. I included schema and tests for dvc. The tests ran fine in the development environment. Additionally, within the environment, the standard dvc functionality (dvc push, dvc pull) with the custom auth header in webdav worked fine. As stated previously, I did not include any version changes.
I also inlcuded a PR for documentation in order to add the functionality to the documentation.
Fix #8931 .
❗ I have followed the Contributing to DVC checklist.
📖 If this PR requires documentation updates, I have created a separate PR (or issue, at least) in dvc.org and linked it here.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏