-
Notifications
You must be signed in to change notification settings - Fork 108
Enable Gxadmin Galaxy clean up cron task #1753
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
Enable Gxadmin Galaxy clean up cron task #1753
Conversation
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.
Pull request overview
This PR enables the Gxadmin Galaxy cleanup cron task by moving it (along with the Docker cleanup task) from a host-specific configuration file to a shared maintenance configuration file, and changing its enable flag from false to true.
- Relocated cron task definitions from
group_vars/sn09/sn09.ymltogroup_vars/maintenance.yml - Enabled the gxadmin Galaxy cleanup task to run every 2 days at midnight
- Added a clarifying comment explaining the gxadmin cleanup purpose
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| group_vars/sn09/sn09.yml | Removed host-specific cron task configurations for Docker and gxadmin cleanup |
| group_vars/maintenance.yml | Added shared cron task configurations, enabling the gxadmin Galaxy cleanup task that removes old histories/hdas |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
I think there is something wrong with this branch..., those commits are already merged, probably needs a rebase. |
50b646d to
04e1d5f
Compare
|
I'm not sure how to fix this ... I did merge master into the current branch locally to sync the changes, didn't know that all commits would show here =/ edit: I did rebase now but I think the commit history wont disappear (?) |
baaaa86 to
c6c19b1
Compare
I hope the state I force-pushed is the one you wanted to reach. If not |
This might impose high load on the db.
xref: #1495