-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SECRET_KEY: fall back to beaker.session.secret #7853
Conversation
@amercader interested in your thoughts on this one. If the uppercase SECRET_KEY is a flask convention should we change envvars so it can generate this option instead? |
I think we should align with Flask and keep the upper case I made a first try in ckanext-envvars, using the config declaration if present (ie CKAN>=2.10) to keep those keys declared as they are when parsing the env vars. This works well in CKAN 2.11 (master) but not in CKAN 2.10. The problem is that I'll keep investigating but does this seem like a good approach to explore? |
@amercader ckan/ckanext-envvars#9 looks good to me. I'll remove the lowercase secret_key part of this PR |
This reverts commit 4160fac but keeps some unrelated fixes
ckanext-envvars 0.0.4 supports upper case config options |
@amercader I merged #7884 so we can see the tests passing, once we merge that to master this will be easier to review |
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin dev-v2.11
git worktree add -d .worktree/backport-7853-to-dev-v2.11 origin/dev-v2.11
cd .worktree/backport-7853-to-dev-v2.11
git switch --create backport-7853-to-dev-v2.11
git cherry-pick -x 4160facd55bedf321b0f32d9b73f57f2aea8730a 1ab96909f6b04f0d90a8bd7ed2758f315dc97b12 1cd72262274895e08a0d835e79f391b3712dddc2 |
Proposed fixes:
Features: