How to hide environment variable in a file base configuration

[jonathan.girard]

I’m currently working with the .toml file to setup environment variables for each branch i’m using.

Since it’s not good practice to push secret keys and ID to GIT, I’m wondering how to you guys hide sensitive information from the .toml file based configuration?

[luke]

Hi, @jonathan.girard, by not putting it in that file.

One alternative is entering those values as environment variables in the web app as site settings (under Site Name > Settings > Build & deploy > Environment). The build system will see those values but they don’t exist in the repository’s tracked files anywhere.

If there are other questions, please let us know.

[rajan-magar]

I tried the same way. But its not working for pem private key. I tried with and without double quotes. Also removed \n from they key but still getting this error.

[luke]

Hi, @rajan-magar, these support guides may be helpful:

[Support Guide] Using an SSH key via environment variable during build

Last checked by Netlify Support Team: December 2022 Some workflows require use of an SSH private key during build - for instance, logging in to a server to restart your backend, or using git clone on a private repo during build. There are better ways to accomplish this goal for most use cases, but in case you choose to do that, below is an approach that can work. First, create an ssh key and add the public key (shorter one) to your service (e.g. on your GitHub repo settings, or in ~/.ssh/auth…

[Support Guide] Using environment variables on Netlify correctly

Last reviewed: August 2023 The preferred way to use environment variables in Netlify is to set them in our environment - be that in the Environment Variables settings UI (on the site’s “Build & Deploy settings” page), or via netlify.toml. You’ll want to choose the right pattern to meet your needs. Setting variables in our UI may be considered a bit more secure, since only people with access to the Netlify admin UI for your site can see them, rather than “anyone who can clone your repo!”. Thes…

If those two topics don’t help to resolve the issue or if there are any questions, please let us know.