You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this moment if we would use CLI command infisical export > .env all env-s will be exported in this pattern ENV_NAME='VALUE' i think it is worth to have possibility to dynamicly change quota character it may makes some issues with ' character
Why would it be useful?
If the value is multiline string with \n single quota character will not parse it as multiline, to have parsed multiline value env have to be in double quotas, i got issue with it when i have passed PRIVATE KEY from google recaptcha, i had to use this function s.replace(/\\n/g, '\n') (in nodejs) to get multiline parsed valid env, otherwise google recaptcha throws me an error
Additional context
Everything is above :D
The text was updated successfully, but these errors were encountered:
Feature description
At this moment if we would use CLI command
infisical export > .env
all env-s will be exported in this patternENV_NAME='VALUE'
i think it is worth to have possibility to dynamicly change quota character it may makes some issues with'
characterWhy would it be useful?
If the value is multiline string with
\n
single quota character will not parse it as multiline, to have parsed multiline value env have to be in double quotas, i got issue with it when i have passed PRIVATE KEY from google recaptcha, i had to use this functions.replace(/\\n/g, '\n')
(in nodejs) to get multiline parsed valid env, otherwise google recaptcha throws me an errorAdditional context
Everything is above :D
The text was updated successfully, but these errors were encountered: