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
What problem are you trying to solve?
we are working with nexus repository 3.74.0 and having several nuget v3 (hosted) repositories. We enabled the cleanup policies for some test repositories and want to delete assets which are older than 10 days.
We hosting chocolatey packages on these feeds and when chocolatey is downloading a asset, its creating a /v3/registration//index.json.
When you deleting a asset from the nexus webgui or api, the registration page/index.json is automatically deleting too.
When you using the cleanup policy, it will delete the asset but not the index.
You can see the issue in this video:
Do you have a workaround you are using at present?
The workaround is a script which is deleting from the api.
What feature or behavior is this required for?
The cleanup policies should have the same behavior when you deleting from the webgui or the api.
Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?
Windows Server 2022
Nexus Repository OSS 3.74
H2 Database
The text was updated successfully, but these errors were encountered:
we are working with nexus repository 3.74.0 and having several nuget v3 (hosted) repositories. We enabled the cleanup policies for some test repositories and want to delete assets which are older than 10 days.
We hosting chocolatey packages on these feeds and when chocolatey is downloading a asset, its creating a /v3/registration//index.json.
Microsoft decscribes that as the “registration page” for nuget v3 specification:
Package Metadata, NuGet API | Microsoft Learn
When you deleting a asset from the nexus webgui or api, the registration page/index.json is automatically deleting too.
When you using the cleanup policy, it will delete the asset but not the index.
You can see the issue in this video:
Do you have a workaround you are using at present?
The workaround is a script which is deleting from the api.
What feature or behavior is this required for?
The cleanup policies should have the same behavior when you deleting from the webgui or the api.
Tell us about your Nexus Repository deployment: what version, operating system, and database are you using?
Windows Server 2022
Nexus Repository OSS 3.74
H2 Database
The text was updated successfully, but these errors were encountered: