Supabase db pull command gives dump file with database triggers making http request with jwt token

[SadmanYasar]

Hi. I am currently facing an issue where the migration file with database triggers that call an edge function with jwt token is included.

The line in migration file:

CREATE OR REPLACE TRIGGER "TRIGGER NAME" AFTER INSERT OR UPDATE ON "public"."table name" FOR EACH ROW EXECUTE FUNCTION "supabase_functions"."http_request"('https://URL/functions/v1/NAME OF FUNCTION', 'POST', '{"Content-type":"application/json","Authorization":"Bearer TOKEN INCLUDED HERE"}', '{}', '5000');

Making the repository public means this key is exposed and becomes a security issue. What can be done to still include the trigger code but hide or remove the token from the migration file? I may be wrong but can the token be passed as environment variable in the migration? Or should the migration files be kept private in this case? TIA.

[SirFrey]

could you do something?