Memcache: PROVIDER_CONFIG
is not restored if altered previously
#453
Labels
No Label
has
backport
in progress
invalid
kind
breaking
kind
bug
kind
build
kind
dependency
kind
deployment
kind
docs
kind
enhancement
kind
feature
kind
lint
kind
proposal
kind
question
kind
refactor
kind
security
kind
testing
kind
translation
kind
ui
need
backport
priority
critical
priority
low
priority
maybe
priority
medium
reviewed
duplicate
reviewed
invalid
reviewed
wontfix
skip-changelog
status
blocked
status
needs-feedback
status
needs-reviews
status
wip
upstream
gitea
upstream
other
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/helm-chart#453
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I just switched from redis-cluster to memcache and noticed that
session.PROVIDER_CONFIG
is not restored to the respective memcache DNS.It is done for
cache.HOST
: https://gitea.com/gitea/helm-chart/src/branch/main/templates/_helpers.tpl#L233 and should most likely be done in the same way forsession.PROVIDER_CONFIG
.Isn't that similar to #356?
Partly as the old config is not removed when switching session providers but the actual issue is that the chart is not defining memcache for session.
I made the issue in a hurry and I just realized that the chart is (most likely on purpose) not setting anything for
config.session
. I thought the default wasmemcache
there as well but now I am not sure anymore...I believe the chart uses the default for sessions. Which is memory.
Good point. Then it's probably only #356 again and I should have set it to
memory
instead ofmemcache
.Given we already have
memcache
, it could also be used forsession
.Closing in favor of #356.