-
Notifications
You must be signed in to change notification settings - Fork 169
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
Helm chart repository previous versions #500
Comments
@mojtabaimani please create a story out of this and it in backlog |
@svatwork I removed your link to a chart releaser action issue, as that was unrelated (feature request to overwrite existing release, which should never happen imo). |
I thought we were using that action, but anyway, I sent a wrong issue, I actually meant this one: helm/chart-releaser-action#70 (ie., chart releases get appended not overwritten). Edit: I now see we use that chart action:
My point is that the feature to append instead of overwrite is in progress. |
I don't see a story here, but do suggest to talk to the 3rd party software owner and check wether this will be, or is already implemented. After doing so the assignee of this issue should put this either "On hold" with a remark that we're waiting for feedback, or just put this issue "in progress" and configure it correctly. @mojtabaimani please from now on always work this way. Please don't let 3rd party software quirks end up as an issue that has no next steps. |
fixed |
Describe the bug:
When making a new otomi chart release, it will override the index.yaml file of the chart repository and doesn't keep the previous versions. But it should just append the new version to the current index.yaml.
To Reproduce
Steps to reproduce the behavior:
Expected behavior: (a clear and concise description of what you expected to happen)
It should update the index.yaml file with the new release and not creating and replacing a new file.
The text was updated successfully, but these errors were encountered: