We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
kargo version
Kargo will constantly add commits to a pull request when using Helm chart.
It updates the Chart.lock file with a need timestamp on the generated field every five minute: generated: "2024-07-01T07:01:59.944058789Z"
Chart.lock
generated: "2024-07-01T07:01:59.944058789Z"
apiVersion: kargo.akuity.io/v1alpha1 kind: Warehouse metadata: name: example namespace: kargo spec: subscriptions: - chart: repoURL: oci://my-acr.azurecr.io/helm-charts/my-app --- apiVersion: kargo.akuity.io/v1alpha1 kind: Stage metadata: name: test namespace: kargo spec: subscriptions: warehouse: example promotionMechanisms: gitRepoUpdates: - repoURL: https://github.com/akselleirv/fake-example.git writeBranch: main pullRequest: github: { } helm: charts: - chartPath: my-app-dir name: my-app repository: oci://my-acr.azurecr.io/helm-charts
v0.7.1
Paste any relevant application logs here.
The text was updated successfully, but these errors were encountered:
I think this touches the same area/problem as #2178.
Sorry, something went wrong.
I am adding this to v0.9.0, as I anticipate that work on #2219 will naturally solve this.
@hiddeco will this still happen with the helm-template promotion step?
helm-template
hiddeco
Successfully merging a pull request may close this issue.
Checklist
kargo version
.Description
Kargo will constantly add commits to a pull request when using Helm chart.
It updates the
Chart.lock
file with a need timestamp on the generated field every five minute:generated: "2024-07-01T07:01:59.944058789Z"
Steps to Reproduce
Version
Logs
The text was updated successfully, but these errors were encountered: