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

Index regeneration on delete doesn't work #365

Closed
akushsky opened this issue Aug 13, 2020 · 4 comments
Closed

Index regeneration on delete doesn't work #365

akushsky opened this issue Aug 13, 2020 · 4 comments

Comments

@akushsky
Copy link

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.

@scbizu
Copy link
Contributor

scbizu commented Aug 13, 2020

Duplicate #22 and #220 ?

@akushsky
Copy link
Author

Duplicate #22 and #220 ?

Totally agree.
We have version system like "10.0.2-112" and could reproduce that issue.

Is there at least workaround for now?

@scbizu
Copy link
Contributor

scbizu commented Aug 16, 2020

Duplicate #22 and #220 ?

Totally agree.
We have version system like "10.0.2-112" and could reproduce that issue.

Is there at least workaround for now?

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.

@scbizu scbizu closed this as completed Apr 22, 2021
@pixelicous
Copy link

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants