Use env vars without it needing to be the entire string.
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- cli
Research direction
No file or test is named. Start by locating the CLI configuration parser and its current env() substitution handling, then reproduce the provided auth configuration with an inline value. Done means inline environment placeholders work in strings while existing full-string env() values continue to work.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
When using branching, it's impossible to properly supply various values based on env vars but also other text.
For example:
[auth.external.google]
[auth]
enabled = true
site_url = "env(SUPABASE_AUTH_SITE_URL)"
additional_redirect_urls = ["env(SUPABASE_AUTH_SITE_URL)/auth/callback"] # This doesn't work!
Describe the solution you'd like
There should be some way to use env() placeholders inline in a string, either as-is or with extended syntax (for example, ${env()} like JS template strings).
Describe alternatives you've considered
Right now, the only alternative is to hardcode everything, which obviously doesn't work for branching.
Additional context
https://github.com/orgs/supabase/discussions/18937
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 526
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 323
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/cli
-
🐛 Bug supabase/cli
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
🐛 Bug supabase/cli
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
📘 Docs supabase/cli
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
🐛 Bug supabase/cli
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
🐛 Bug supabase/cli
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Doist/todoist-cli#576 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
CopilotKit/aimock#491 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
agilepathway/label-checker#710 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Community-VyProjects/VyManager#908 ·
Maintainers usually reply within 1 day