theskumar / theskumar/python-dotenv
Connection string in .env-file not read or parsed properly
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Python
- Estrellas
- 8.9k
- Forks
- 581
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
Hi,
I have an azure blob storage connection string stored in my .env file, as follows:
CONNECT_STRING_BLOB="DefaultEndpointsProtocol=https;AccountName=xxxx;AccountKey=asdfasdfasdf/asdfasdfdsafdas/asdfadsfdsaf/ads==;EndpointSuffix=core.windows.net;"
Recently I'm experiencing very spotty behavior where me and/or colleagues on similar setups have different results:
Sometimes parsed as DefaultEndpointsProtocol sometimes as the full connect string.
- Workaround has been: to replace
CONNECT_STRING_BLOBtoCONNECTSTRINGBLOB, but implementing this change everywhere is not an option, and more importantly it does not always solves the issue - Workaround has been as well to remove "_" and place it back, but that does not work always either.
- Executing the file with the debugger in VS Code solves the issue somewhat consistently.
Not sure even if this is a python-dotenv issue, but I have litterally no clue anymore where to look as it's so inconsistent and cant seem to find a solution for it.
We have the same requirements file installed, including latest python-dotenv.
Python 3.8.10
Ubuntu-20.04 on WSL1
working in Visual Studio Code (if that even matters)
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Start by reproducing the .env parsing with the shown Azure Blob connection string under Python 3.8.10 on Ubuntu 20.04 in WSL1, comparing normal execution with the VS Code debugger. Check whether the parsed value changes with the variable name or execution context; done means the cause is identified and parsing is consistent, with the behavior verified in a focused regression test.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- azure, python
- Área
- tooling
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100