Closed
Conversation
secana
approved these changes
Feb 20, 2026
Member
|
Hi! What do we gain by moving the signing key from one secret to another? |
Author
|
Hi secana! That's because 1. I use a config map for the environment variables and 2. a wrapper helm chart to deploy. I created an external secret in the wrapper for the postgres password secret. Hence, why I was trying to make the cookieSigningKey a secret similar to the postgres password. If this doesn't make sense, feel free to close. |
added 2 commits
February 25, 2026 13:59
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Wanted to replicate the postgres password secret logic for the cookieSigningKey.