-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat(deployment): Regular DB maintenance #401
base: main
Are you sure you want to change the base?
Conversation
# Just for testing purposes | ||
repository: db-maintenance | ||
tag: "local" | ||
pullPolicy: "never" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to discuss schedule interval.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thats fine from my perspective once a minute is a bit often though....
Maybe you rather say once at 1 : 30 at night per default:
schedule: "30 1 * * *"
TRUNCATE TABLE IssueMatch; | ||
TRUNCATE TABLE Evidence; | ||
TRUNCATE TABLE ComponentInstance; | ||
TRUNCATE TABLE IssueVariant; | ||
TRUNCATE TABLE ComponentVersion; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TRUNCATE TABLE IssueMatch; | |
TRUNCATE TABLE Evidence; | |
TRUNCATE TABLE ComponentInstance; | |
TRUNCATE TABLE IssueVariant; | |
TRUNCATE TABLE ComponentVersion; | |
TRUNCATE TABLE IssueMatch; | |
TRUNCATE TABLE Evidence; | |
TRUNCATE TABLE ComponentInstance; | |
TRUNCATE TABLE IssueVariant; | |
TRUNCATE TABLE ComponentVersion; |
Not sure about these ones.
# Just for testing purposes | ||
repository: db-maintenance | ||
tag: "local" | ||
pullPolicy: "never" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thats fine from my perspective once a minute is a bit often though....
Maybe you rather say once at 1 : 30 at night per default:
schedule: "30 1 * * *"
I think this PR should rather be in https://github.wdf.sap.corp/cc/heureka. This functionality is only SAP related. I'll close this one and create new one in GH enterprise. |
Description
We should clean-up the Heureka Db regularly in order to be able to scan periodically.
What type of PR is this? (check all applicable)
Related Tickets & Documents
Added tests?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Added to documentation?
Checklist