chore: disable workflow logs auto-cleanup by default

[laipz8200]

Summary

This PR changes the default value of WORKFLOW_LOG_CLEANUP_ENABLED from true to false across all configuration files.

Changes

• api/configs/feature/init.py: Changed WorkflowLogConfig.WORKFLOW_LOG_CLEANUP_ENABLED default from True to False
• api/.env.example: Changed WORKFLOW_LOG_CLEANUP_ENABLED from true to false

Note: docker/.env.example and docker/docker-compose.yaml already had the correct default value of false.

Motivation

Setting the default to false provides safer default behavior by:

• Preventing unintended data loss for new installations
• Giving users explicit control over when to enable log cleanup
• Following the opt-in principle for data deletion features

Users who need automatic cleanup can enable it by setting WORKFLOW_LOG_CLEANUP_ENABLED=true in their configuration.

Fixes #28135

[gemini-code-assist]

Summary of Changes

Hello @laipz8200, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request modifies the default behavior of workflow log cleanup, switching it from enabled to disabled. This change is a proactive measure to prevent accidental data loss for new installations and to empower users with explicit control over data retention. By making log cleanup an opt-in feature, the system prioritizes data preservation and user choice.

Highlights

• Default Workflow Log Cleanup: The default value for WORKFLOW_LOG_CLEANUP_ENABLED has been changed from true to false in api/.env.example and api/configs/feature/__init__.py.
• Enhanced Data Safety: This change prevents unintended data loss for new installations and gives users explicit control over enabling log cleanup, aligning with an opt-in principle for data deletion features.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request changes the default behavior of workflow log cleanup by setting WORKFLOW_LOG_CLEANUP_ENABLED to false. This is a sensible and safe change, as it prevents accidental data loss for new installations and makes log cleanup an opt-in feature. The changes in api/.env.example and api/configs/feature/__init__.py are correct and align with the stated goal.

While reviewing the related code, I noticed that the Celery task clean_workflow_runlogs_precise in api/schedule/clean_workflow_runlogs_precise.py does not check the WORKFLOW_LOG_CLEANUP_ENABLED flag internally. While the check is likely performed by the scheduler, for added safety, you might consider adding a check at the beginning of the task itself in a future PR to prevent accidental execution if the task is triggered manually.

[QuantumGhost]

LGTM.

Thank you for your contribution!