You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
From trying to write end-to-end tests with
pelican object put
we discovered that it relies on knowing whatTopology.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.The text was updated successfully, but these errors were encountered: