-
Notifications
You must be signed in to change notification settings - Fork 400
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
Index regeneration on delete doesn't work #365
Comments
I have fixed it at #362 , and still waiting @jdolitsky for some reviewing . For now , you should avoid this kind of version number until the patch merge into master and spawn the new release. |
Still encounter this problem, new chart museum version and deployment |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I try to delete a chart
curl -XDELETE http://192.168.1.1:8080/api/charts/mychart/1.2.3
It always returns
{"deleted":true}
, deletes file from the storage, but in index-cache.yaml it only changes the generation time, without removing entry with deleted chart version. That's really an unexpected behavior.My chartmuseum version is 0.12.0 (build 101e26a) and I use S3 as backend storage.
The text was updated successfully, but these errors were encountered: