Skip to content

feat: add gitops-operator-default pulling interval #456

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

Merged
merged 3 commits into from
Apr 22, 2025

Conversation

kim-codefresh
Copy link
Contributor

What

Why

Notes

@kim-codefresh kim-codefresh requested review from a team as code owners April 22, 2025 10:31
@@ -662,7 +662,9 @@ gitops-operator:
# -- Additional labels for gitops operator CRDs
additionalLabels: {}

env: {}
env: {
TASK_PULLING_INTERVAL: 10s
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we are looking for POLLING term

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, at the moment the field is task-pulling-interval, and by default the env var is TASK_PULLING_INTERVAL
in a pr i am currently working on, i fixed the field + env var to use "polling". once i merge it, i will make sure to also update the env var in gitops-runtime-helm accordingly.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah I just had to match the current value, @ATGardner if you can put your self some note to fix it in the next runtime

Comment on lines 79 to 82
{{/* Set DEFAULT_TASK_PULLING_INTERVAL */}}
{{- if not (index .Values "gitops-operator").env.TASK_PULLING_INTERVAL }}
{{- $_ := set $gitopsOperatorContext.Values.env "TASK_PULLING_INTERVAL" "10s" }}
{{- end }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need this template bit?
wouldn't just adding it to the values.yaml under gitops-operator.env be enough to set it as a default value?

@kim-codefresh
Copy link
Contributor Author

/e2e

@kim-codefresh kim-codefresh merged commit a79d213 into main Apr 22, 2025
2 checks passed
@kim-codefresh kim-codefresh deleted the feat/gitops-operator-default-pull-interval branch April 22, 2025 12:48
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

Successfully merging this pull request may close these issues.

5 participants