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

Add ttlSecondsAfterFinished to migrateDatabaseJob and createUserJob #29314

Merged

Conversation

alexandermalyga
Copy link
Contributor

related: #27561

Adds the ttlSecondsAfterFinished parameter to migrateDatabaseJob and createUserJob, so job objects can be automatically deleted after execution.

@@ -48,6 +48,9 @@ metadata:
{{- $annotations | toYaml | nindent 4 }}
{{- end }}
spec:
{{- if not (kindIs "invalid" .Values.createUserJob.ttlSecondsAfterFinished) }}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Checking specifically for not nil because 0 is a valid value for this field and it would evaluate to false normally.

@potiuk
Copy link
Member

potiuk commented Feb 13, 2023

Ah, I missed that one and it's a better fix than mine #29439

Copy link
Member

@potiuk potiuk left a comment

Choose a reason for hiding this comment

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

This is better than mine - also @hussein-awala suggest that we could rename the jobs so that it will also work even if update is done quickly. See #29439 (review)

chart/values.yaml Outdated Show resolved Hide resolved
Copy link
Member

@potiuk potiuk left a comment

Choose a reason for hiding this comment

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

OK. Pending the two small comments @dstandish @jedcunningham - in case you think there is a reason why job name cannot be changed, pleas shout :)

@alexandermalyga
Copy link
Contributor Author

This is better than mine - also @hussein-awala suggest that we could rename the jobs so that it will also work even if update is done quickly. See #29439 (review)

I tried and this affects a lot of tests, let's do it in a separate PR?

@potiuk
Copy link
Member

potiuk commented Feb 13, 2023

This is better than mine - also @hussein-awala suggest that we could rename the jobs so that it will also work even if update is done quickly. See #29439 (review)

I tried and this affects a lot of tests, let's do it in a separate PR?

I am fine with it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:helm-chart Airflow Helm Chart
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants