We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug The env() function to load environment variables into the config.toml does not work for arrays in the config.toml.
env()
config.toml
To Reproduce Steps to reproduce the behavior:
[db.seed] enabled = true sql_paths = [ "env(SEEDS_PATH)" ]
SEEDS_PATH=abc123 supabase db reset
No seed files matched pattern: supabase/env(SEEDS_PATH)
Expected behavior Supabase uses the path in the environment variable to source database seeds.
System information Rerun the failing command with --create-ticket flag.
--create-ticket
SEEDS_PATH=abc123 supabase db reset --create-ticket
SERVICE IMAGE │ LOCAL │ LINKED ─────────────────────────┼──────────────────┼───────────── supabase/postgres │ 15.1.0.122 │ 15.1.0.122 supabase/gotrue │ v2.162.1 │ v2.162.1 postgrest/postgrest │ v11.2.0 │ v11.2.0 supabase/realtime │ v2.30.34 │ - supabase/storage-api │ v1.11.7 │ v1.11.14 supabase/edge-runtime │ v1.58.12 │ - supabase/studio │ 20240930-16f2b8e │ - supabase/postgres-meta │ v0.83.2 │ - supabase/logflare │ 1.4.0 │ - supabase/supavisor │ 1.1.56 │ -
Additional context I have tested this with a .env file as well, with no luck.
.env
Related issues include:
These issues are related but distinct -- as far as I can tell there is no issue for this array-specific bug.
The text was updated successfully, but these errors were encountered:
I've run into the same issue
Sorry, something went wrong.
No branches or pull requests
Describe the bug
The
env()
function to load environment variables into the config.toml does not work for arrays in theconfig.toml
.To Reproduce
Steps to reproduce the behavior:
config.toml
SEEDS_PATH=abc123 supabase db reset
No seed files matched pattern: supabase/env(SEEDS_PATH)
in the console output. This is the first line in the output.Expected behavior
Supabase uses the path in the environment variable to source database seeds.
System information
Rerun the failing command with
--create-ticket
flag.SEEDS_PATH=abc123 supabase db reset --create-ticket
Additional context
I have tested this with a
.env
file as well, with no luck.Related issues include:
These issues are related but distinct -- as far as I can tell there is no issue for this array-specific bug.
The text was updated successfully, but these errors were encountered: