Skip to content

Conversation

@tuteng
Copy link
Member

@tuteng tuteng commented Jul 28, 2025

(If this PR fixes a github issue, please add Fixes #<xyz>.)

Fixes #

(or if this PR is one task of a github issue, please add Master Issue: #<xyz> to link to the master issue.)

Master Issue: #

Motivation

Explain here the context, and why you're making that change. What is the problem you're trying to solve.

Modifications

Describe the modifications you've done.

Verifying this change

  • Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

  • Added integration tests for end-to-end deployment with large payloads (10MB)
  • Extended integration test for recovery after broker failure

Documentation

Check the box below.

Need to update docs?

  • doc-required

    (If you need help on updating docs, create a doc issue)

  • no-need-doc

    (Please explain why)

  • doc

    (If this PR contains doc changes)

@tuteng tuteng requested review from a team as code owners July 28, 2025 00:28
@github-actions
Copy link

@tuteng:Thanks for your contribution. For this PR, do we need to update docs?
(The PR template contains info about doc, which helps others know more about the changes. Can you provide doc-related info in this and future PR descriptions? Thanks)

@github-actions github-actions bot added the doc-info-missing This pr needs to mark a document option in description label Jul 28, 2025
@labuladong labuladong requested a review from Copilot July 28, 2025 00:41
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

This PR introduces a new configuration option readTokenFromFile to control how JWT authentication tokens are provided to the sn-platform components. The change allows users to choose between reading tokens from files (existing behavior) or from Kubernetes secrets (new behavior).

  • Added readTokenFromFile: false configuration option to JWT authentication settings
  • Modified authentication parameter logic to conditionally use file-based or secret-based token access
  • Updated secret mounting logic to only mount token secrets when file-based reading is enabled

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File Description
charts/sn-platform/values.yaml Added readTokenFromFile configuration option with default value false
charts/sn-platform/templates/_helpers.tpl Updated authentication logic to support both file and secret-based token reading
charts/sn-platform-slim/values.yaml Added readTokenFromFile configuration option with default value false
charts/sn-platform-slim/templates/_helpers.tpl Updated authentication logic to support both file and secret-based token reading

@tuteng
Copy link
Member Author

tuteng commented Aug 21, 2025

dup with #1230

@tuteng tuteng closed this Aug 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc-info-missing This pr needs to mark a document option in description

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants