fix(helm): remove config overrides for CSRF #22716
Merged
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.
SUMMARY
Fixes #22715
This PR removes the
WTF_
CSRF-related overrides from the configuration file generated by the Helm chart, allowing the defaults fromconfig.py
to be used.superset/superset/config.py
Lines 249 to 257 in 2ccdb72
As noted in #22715, there may be better ways to handle the CSRF exclusion for these three routes outside of the config file to prevent this same mistake from being made in other context. This is just the simplest solution that solves the issue with the Helm chart clearing the list.
TESTING INSTRUCTIONS
/superset/log
are returning 200 instead of 302 redirects to/login
ADDITIONAL INFORMATION