Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Sonatype Nexus remote repository support #5528

Closed
Nantero1 opened this issue Feb 26, 2021 · 5 comments
Closed

Add Sonatype Nexus remote repository support #5528

Nantero1 opened this issue Feb 26, 2021 · 5 comments
Labels
feature request Requesting a new feature p3-nice-to-have It should be done this or next sprint

Comments

@Nantero1
Copy link

Sonatype Nexus is a famous and widely used repository manager used to securely store packages and has an excellent user access control.

Usually it is used to host R, Java, Python and other build artifacts. Nevertheless, its hosted RAW repository type allows it to store any files and data!
It would be nice to add this famous, tested and flexible artifactory as a remote storage type to DVC and be able store ML data.

image

@efiop efiop added feature request Requesting a new feature p3-nice-to-have It should be done this or next sprint labels Feb 26, 2021
@Nantero1
Copy link
Author

Nantero1 commented Feb 26, 2021

@efiop Privet Ruslan 👍 I reaaaaally like DVC! Thanks for this tool!
This feature-request is not just wishful thinking, I actually implemented this already- I'm running all pre-commit hooks to make a Pull request with this feature included. Please give me some more minutes 🚀

Was not expecting someone to react so quickly 😄

@efiop
Copy link
Contributor

efiop commented Feb 27, 2021

Hi @BenLinnik !

Please note that we are migrating to fsspec #5162 and there are a few remote PRs pending already for other clouds (e.g. osf, dropbox, etc). We will not be merging new implementations unless they comply with fsspec. At the same time it is becoming harder and harder for dvc team to maintain quality support for the variety of clouds on our own, so the absolute best way to go about it would be for you to follow fsspec and maintain your implementation (e.g. how s3fs does it) in your own package (and also maybe try to get it accepted into https://github.com/intake/filesystem_spec/tree/master/fsspec/implementations). That way it will be really easy for us to accept it, or, if our plugin mechanism will be ready by that time, just use your implementation automatically through fsspec registry or some explicit option.

@Nantero1
Copy link
Author

Oh ok, this is new to me. I will have a look into it. Please keep up the good work!

@efiop
Copy link
Contributor

efiop commented Feb 27, 2021

@BenLinnik Thank you! 🙏 And sorry for making you now adapt your PR again, we are in the middle of migrating ourselves, so there is a mixup in the code 🙁 We'll document it properly in the contribution guide after the 2.0 release. Thanks again for contributing!

@efiop
Copy link
Contributor

efiop commented Dec 8, 2023

Doesn't seem like there is much demand for this at all. Closing.

@efiop efiop closed this as completed Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Requesting a new feature p3-nice-to-have It should be done this or next sprint
Projects
None yet
Development

No branches or pull requests

2 participants