Nasim SadatandClaude Opus 5.5
1b8e57adb4
Baseline before the clean-up (PD-13): the PD-11 reader setup and the PD-12 app dashboards as they ran on the local stack, uncommitted until now. Not deployed, not independently reviewed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
990 B
990 B
patches/
Runtime patches applied while the Superset image is built
(stacks/fuel-monitoring/superset/Dockerfile):
fix_redact_query_for_readers.py: chart-data responses carry no SQL for readers, as Superset already does for embedded guests (petrolyst_reader.py).
Same convention as media-insights:
- One file per fix, named
fix_<what>.py. It patches files inside the installed image (/app/superset/...or the venv), for changes that cannot be made throughsuperset_config.py. python3 fix_<what>.pyapplies the patch;python3 fix_<what>.py --verifyexits non-zero unless the patched code is in place. Both must be idempotent.- The Dockerfile runs both for every
fix_*.pyand stops at the first failure, so a patch that no longer applies to a new Superset version fails the build instead of shipping silently. - Everything in this folder is a build input: changing it gives the image a new tag and
recreates the
supersetcontainer on the next deploy.