-
Notifications
You must be signed in to change notification settings - Fork 7.2k
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
Proposal: Allow a way to create an idempotent index.yaml file #11057
Comments
@colearendt Can you create a HIP for this feature. Thanks very much. |
Woops missed that process 😅 Thanks, will do! |
This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs. |
I started a HIP for this - haven't submitted yet |
This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs. |
I started on a HIP for this. Need to finish! |
This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs. |
Grr. My HIP is stagnant. Still hoping to get back to this 🙈 |
This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs. |
Still hoping to get back here |
This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs. |
Per discussion here, there is reluctance to depend on filesystem times for chart "created" time.
However, there are other occasions where being able to create an index.yaml file from a set of data that is reliable (i.e. GitHub tags, releases, git logs, etc.). As a result, it would be ideal to have a way to generate the index file in an idempotent fashion.
I believe the only piece of data that is not reproducible is the "created" time. As a result, it would be ideal to have a way to
IndexFile.MustAdd()
with deterministic input / output (i.e. allow specifying the timestamp). This would allow index file creation to be idempotent downstream, which could improve CI mechanisms, migration to different build systems, and migration to different helm repositories without losing timestamp data.Relevant code:
helm/pkg/repo/index.go
Lines 120 to 146 in 657850e
Would a PR implementing such a solution be permissible? What approach would be preferable?
The text was updated successfully, but these errors were encountered: