Skip to content
This repository has been archived by the owner on Jan 24, 2023. It is now read-only.

Configurable backend log level #2533

Merged
merged 2 commits into from
Jun 27, 2018
Merged

Configurable backend log level #2533

merged 2 commits into from
Jun 27, 2018

Conversation

irfanhabib
Copy link
Contributor

@irfanhabib irfanhabib commented Jun 27, 2018

  1. Allows user to set the log level of the Jetstream
  2. Enables debug logging in docker-compose deployment

@cfdreddbot
Copy link

Hey irfanhabib!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA.

@codecov
Copy link

codecov bot commented Jun 27, 2018

Codecov Report

Merging #2533 into v2-master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           v2-master    #2533   +/-   ##
==========================================
  Coverage      70.44%   70.44%           
==========================================
  Files            594      594           
  Lines          25124    25124           
  Branches        5671     5671           
==========================================
  Hits           17698    17698           
  Misses          7426     7426

Copy link
Contributor

@nwmac nwmac left a comment

Choose a reason for hiding this comment

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

Small questions/comments otherwise LGTM

@@ -159,6 +159,10 @@ spec:
{{- if .Values.socksProxy }}
value: {{.Values.socksProxy}}
{{- end }}
- name: LOG_LEVEL
Copy link
Contributor

Choose a reason for hiding this comment

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

Shouldn't the name be inside the if?

Copy link
Contributor Author

@irfanhabib irfanhabib Jun 27, 2018

Choose a reason for hiding this comment

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

The default value specified is info, if that is unset, we will still default to 'info'.

deploy/proxy.env Outdated
@@ -21,3 +21,4 @@ SESSION_STORE_SECRET=wheeee!
CONSOLE_PROXY_CERT_KEY=use local dev-cert/pproxy.key in portal-proxy repo
CONSOLE_PROXY_CERT=use local dev-cert/pproxy.crt in portal-proxy repo
ENCRYPTION_KEY=B374A26A71490437AA024E4FADD5B497FDFF1A8EA6FF12F6FB65AF2720B59CCF
LOG_LEVEL=debug
Copy link
Contributor

Choose a reason for hiding this comment

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

This will mean any docker compose deployment will have debug logging. Probably want to set this to info.

Should look to see if we can pass this as an env when running standupdevenv

Copy link
Contributor Author

@irfanhabib irfanhabib Jun 27, 2018

Choose a reason for hiding this comment

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

That was the intent, since docker-compose environments are dev environments. I'll move this to the standupdevenv and restart-proxy script.

Copy link
Contributor

@nwmac nwmac left a comment

Choose a reason for hiding this comment

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

LGTM

@nwmac nwmac merged commit 8b7d5a4 into v2-master Jun 27, 2018
@nwmac nwmac deleted the set-log-level branch June 27, 2018 12:40
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants