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

Pelican object copy always relies on topology #504

Closed
joereuss12 opened this issue Dec 14, 2023 · 0 comments · Fixed by #622
Closed

Pelican object copy always relies on topology #504

joereuss12 opened this issue Dec 14, 2023 · 0 comments · Fixed by #622
Assignees
Labels
bug Something isn't working
Milestone

Comments

@joereuss12
Copy link
Contributor

From trying to write end-to-end tests with pelican object put we discovered that it relies on knowing what Topology.NamespaceUrl is set to. This should not be the case since object copy should work without topology. Therefore, need to keep stashcp working with Topology.NamespaceUrl automatically (to keep backwards compatibility) but for osdf and pelican modes to not rely on it and take a different path, asking the director for the information needed rather than topology.

@joereuss12 joereuss12 self-assigned this Dec 14, 2023
@joereuss12 joereuss12 added this to the v7.4.0 milestone Dec 14, 2023
@joereuss12 joereuss12 added the bug Something isn't working label Dec 15, 2023
@joereuss12 joereuss12 linked a pull request Dec 20, 2023 that will close this issue
@joereuss12 joereuss12 linked a pull request Jan 8, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant