Restore indices cronjob template is tied to No Code migration flag
Gerrit-K opened this issue · 8 comments
Is your feature request related to a problem? Please describe.
The datahub-restore-indices-job-template is a useful tool to restore Graph indices from the database, as described here. However, the template is surrounded by a {{- if .Values.datahubUpgrade.enabled -}}, which ties it to the No Code migration.
The No Code migration, as far as I've understood, is quite an old topic that should not apply to freshly set up DataHub environments. Therefore, it doesn't make sense to enable that job (especially since it's run on every helm update), but it would be nice to keep the restore indices cronjob template, even when the No Code migration is disabled.
Describe the solution you'd like
Remove the condition around the cronjob template.
This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io
Not stale.
Chart version 0.3.25
This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io
Not stale.
Chart version 0.3.28
This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io
Not stale.
Chart version 0.4.0
This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io
This issue was closed because it has been inactive for 30 days since being marked as stale.