Uh oh!
There was an error while loading. Please reload this page.
feat: lifecycle configuration control plane - #1338
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Coverage Report for CI Build 32860587778Coverage increased (+0.4%) to 81.687%Details
Uncovered Changes
Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
316c6d8 to
3a7d9ceCompareferhatelmas
commented
Aug 18, 2026
@claude always review |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Signed-off-by: ferhat elmas <elmas.ferhat@gmail.com>
Signed-off-by: Ferhat Elmas <elmas.ferhat@gmail.com>
3a7d9ce to
10e3120Compare| EXECUTE format( | ||
| 'CREATE TRIGGER protect_bucket_control_insert BEFORE INSERT ON storage.buckets FOR EACH ROW EXECUTE FUNCTION storage.protect_bucket_control_columns(%L)', | ||
| service_role | ||
| ); |
There was a problem hiding this comment.
@GuptaManan100 this was working a week ago but now it's failing with
EXECUTE of a runtime-built statement inside a PL/pgSQL body is not supported: the statement text is not a constant, so it cannot be checked for unsafe session-state changes
is it expected?
There was a problem hiding this comment.
MT_UNSAFE_POOLER_MODE: "true" seems silencing it but does it have any drawbacks to be aware of?
There was a problem hiding this comment.
For completeness, it fails its first example in https://github.com/supabase/storage/blob/master/migrations/tenant/0002-storage-schema.sql but we can't change old migrations.
This commit seems working, 64dd33d
Signed-off-by: Ferhat Elmas <elmas.ferhat@gmail.com>
What kind of change does this PR introduce?
feat
What is the new behavior?
Add schema for lifecyle configuration and REST/S3 routes to get/put/delete gated by global feature flag.