inconsistent behavior when # in .env container/native #30

New Issue

koalp · 2021-04-30T23:23:05+02:00

koalp commented

2021-04-30 23:23:05 +02:00

Description

When using a password containing a "#", when running using the feature provided by the dotenv crate (sourcing the .env), it fails and you have to put ' around the variable to make it work

However, when using a container image with the --env-file and the .env, you have to remove the ' in order for it to work.

It have been tested in zsh.

Steps to reproduce

Have a password (or url) with '#' in it
Run with the .env, in zsh (or sh).
Run the container image with the --env-file option. (using podman)

Expected behavior
The two methods should have the same behavior.

**Description** When using a password containing a "#", when running using the feature provided by the `dotenv` crate (sourcing the `.env`), it fails and you have to put `'` around the variable to make it work However, when using a container image with the `--env-file` and the `.env`, you have to remove the `'` in order for it to work. It have been tested in zsh. **Steps to reproduce** 1. Have a password (or url) with '#' in it 2. Run with the `.env`, in zsh (or sh). 3. Run the container image with the `--env-file` option. (using podman) **Expected behavior** The two methods should have the same behavior.

koalp added the

labels 2021-04-30 23:23:05 +02:00

koalp self-assigned this 2021-05-13 20:48:13 +02:00

koalp added

status

accepted

and removed

status