Skip to content

Conversation

@churnikov
Copy link
Contributor

Useful in development environment

@churnikov churnikov requested a review from a team as a code owner July 10, 2025 09:11
@churnikov churnikov requested a review from Copilot July 10, 2025 09:21
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

Adds an explicit DEVELOP_LOGS_ENABLED flag to the studio settings ConfigMap to control logging behavior in development.

  • Introduces DEVELOP_LOGS_ENABLED alongside DEBUG in the ConfigMap
  • Switches various logging, Celery, and middleware conditionals from DEBUG to DEVELOP_LOGS_ENABLED
Comments suppressed due to low confidence (3)

serve/templates/studio-settings-configmap.yaml:49

  • The DEVELOP_LOGS_ENABLED flag is still tied to .Values.studio.debug, so it isn’t truly explicit. Reference a new Helm value (e.g. .Values.studio.developLogsEnabled) here so users can control it independently of DEBUG.
    DEVELOP_LOGS_ENABLED = True

serve/templates/studio-settings-configmap.yaml:150

  • [nitpick] Indentation for this middleware entry should align with the other INSTALLED_APPS list items to keep the YAML readable and consistent.
        + (STRUCTLOG_MIDDLEWARE if not DEVELOP_LOGS_ENABLED else [])

serve/templates/studio-settings-configmap.yaml:49

  • Consider adding unit or integration tests to verify that DEVELOP_LOGS_ENABLED toggles logging, Celery, and middleware inclusion as expected in both true and false scenarios.
    DEVELOP_LOGS_ENABLED = True

@churnikov churnikov merged commit 351ac1b into develop Jul 10, 2025
1 check passed
@churnikov churnikov deleted the SS-1250-add-explicit-flag-for-develop-logs branch July 10, 2025 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants