Skip to content
New issue

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

dotenv appears unmaintained and does not support multiline values #2350

Closed
1 of 8 tasks
arjenzorgdoc opened this issue Jan 20, 2025 · 1 comment · Fixed by #2351
Closed
1 of 8 tasks

dotenv appears unmaintained and does not support multiline values #2350

arjenzorgdoc opened this issue Jan 20, 2025 · 1 comment · Fixed by #2351

Comments

@arjenzorgdoc
Copy link

CLI Version

2.38.0

Operating System and Architecture

  • macOS (arm64)
  • macOS (x86_64)
  • Linux (i686)
  • Linux (x86_64)
  • Linux (armv7)
  • Linux (aarch64)
  • Windows (i686)
  • Windows (x86_64)

Operating System Version

Ubuntu 22.04.5 LTS

Link to reproduction repository

No response

CLI Command

No response

Exact Reproduction Steps

$ cat > .env << EOF
PRIVATE_KEY1="-----BEGIN PRIVATE KEY-----
...
-----END PRIVATE KEY-----"
EOF
$ sentry-cli --version
  WARN    2025-01-20 15:40:08.039875680 +01:00 Failed to load .env file: Error parsing line: '"', error at line index: 0
sentry-cli 2.38.0

See this similar PR in an unrelated project: oscope-dev/scope#107

Expected Results

Support multiline env vars.

Actual Results

A warning:

  WARN    2025-01-20 15:40:08.039875680 +01:00 Failed to load .env file: Error parsing line: '"', error at line index: 0

Logs

  WARN    2025-01-20 15:40:08.039875680 +01:00 Failed to load .env file: Error parsing line: '"', error at line index: 0
@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Jan 20, 2025
szokeasaurusrex added a commit that referenced this issue Jan 21, 2025
Replace the unmaintained crate `dotenv` with the maintained fork `dotenvy`.

Fixes #2350
@szokeasaurusrex
Copy link
Member

Thanks for reporting, @arjenzorgdoc, we have already merged a PR which will fix the problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants