chore: add dummy jwt secret

[shivanshuraj1333]

fixes: #6763

Currently if JWT_SECRET is not setup through env variable, it breaks the frontend.

Important

Adds a dummy JWT secret to be used if no JWT secret is specified, with warnings logged for production environments.

• Behavior:
  • Adds a dummy JWT secret SIGNOZ_JWT_SECRET in auth.go to be used if no JWT secret is specified.
  • Updates main.go in both ee/query-service and pkg/query-service to set auth.JwtSecret to SIGNOZ_JWT_SECRET if the environment variable SIGNOZ_JWT_SECRET is not set.
  • Logs a warning if the dummy JWT secret is used, advising to specify a secret in production.

^{This description was created by for 9f4af9f. It will automatically update as commits are pushed.}

[request-info]

We would appreciate it if you could provide us with more info about this issue/pr!

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 9f4af9f in 1 minute and 43 seconds

More details

• Looked at 46 lines of code in 3 files
• Skipped 0 files when reviewing.
• Skipped posting 3 drafted comments based on config settings.

1. ee/query-service/main.go:184

• Draft comment:
  Using a hardcoded dummy JWT secret is a security risk. Ensure this is only used for development and not in production environments.
• Reason this comment was not posted:
  Comment did not seem useful.

2. pkg/query-service/main.go:102

• Draft comment:
  Using a hardcoded dummy JWT secret is a security risk. Ensure this is only used for development and not in production environments.
• Reason this comment was not posted:
  Marked as duplicate.

3. pkg/query-service/constants/auth.go:7

• Draft comment:
  Use design tokens or predefined color constants instead of hardcoding color values to maintain consistency in design and theming.
• Reason this comment was not posted:
  Comment was on unchanged code.

Workflow ID: wflow_nViP1FFGdflnenDl

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.