0

We are using Gitlab in the new company I started and is something new for me, I am not a devops guy but before collaborating with devops and using Octopus Deploy I was able to setup secrets per environment, add them as sensitive so it's hidden and it would be handled on deploy to substitute the values based on environment configuration.

I can always checkin appsettings.{environment}.json configuration files in source code but this opens a hackers party even for a private environment, also the developers shouldn't view UAT and production variables.

Is there an equivalent way or practice on Gitlab to store/load secrets and substitute on deployment per environment?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.