search

Infisical / infisical

♾ Infisical is the open-source secret management platform: Sync secrets across your team/infrastructure, prevent secret leaks, and manage internal PKI
https://infisical.com
Other
14.94k stars 840 forks source link

Possibility to export env-s with different quota character #1103

Open newadbie opened 10 months ago

newadbie commented 10 months ago

Feature description

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

akhilmhdh commented 10 months ago

@newadbie Yah there is a skipMultiEncoding to address these kinda issues but sadly its not yet available for cli. Good issue

sp6370 commented 10 months ago

Hi @akhilmhdh! I would like to pick this up.

Could you expand upon using skipMultiEncoding?

lalitkumawat1m commented 10 months ago

Hello Team I want to work on this issue please assign to me