Menu
I'm using curl to deploy an artifact to a repository and on the initial PUT the artifact successfully gets deployed to the repo. When I try to PUT the same artifact to the same repo I get a 404 "Could not locate artifact". If I go through the UI I can deploy the same artifact to the same repo and everything works.
Any ideas?
803
If a package is not found in those repositories, Artifactory will merge metadata from the repositories that have not been set with the Priority Resolution field.
Artifactory is a branded term to refer to a repository manager that organizes all of your binary resources. These resources can include remote artifacts, proprietary libraries, and other third-party resources. A repository manager pulls all of these resources into a single location.
"Zapping" a cache means forcing the Retrieval Cache Period and Missed Retrieval Cache Period to time out. To "zap" a cache, in the Artifacts module Tree browser, Select the repository cache you wish to "zap" and click Zap caches in the right-click menu or Actions drop-down menu.
This can happen in a situation when:
In such a case, for the first deployment the user has all the required permissions (deploy) and therefore the initial deployment succeeds.
For the second deployment, the user needs delete permissions in order to override the existing artifact. This would normally fail with a 403 status and the following message: "Not enough permissions to overwrite artifact". However, when "Hide existence of unauthorized resources" is checked you get will get a 404 since the deployment operation is unauthorized.
Granting the deploying user delete permission on the target repository should solve this problem (Admin->Security->Permissions).
133
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
