include-env: Include the value of an environment variable at compile time

[ bsd3, development, library ] [ Propose Tags ]

Embed secrets (e.g. API keys) inside production artifacts at compile time.


[Skip to Readme]
Versions [RSS] [faq] 0.1.0.0, 0.1.1.0, 0.1.2.0, 0.1.3.0, 0.2.0.0, 0.3.0.0, 0.4.0.0, 0.5.0.0 (info)
Change log Changelog.md
Dependencies base (>=4.7 && <5), containers, template-haskell (>=2.14), th-lift-instances [details]
License BSD-3-Clause
Copyright (c) 2021 Marco Zocca, UnfoldML AB
Author Marco Zocca
Maintainer oss@unfoldml.com
Category Development
Home page https://github.com/unfoldml/include-env
Source repo head: git clone https://github.com/unfoldml/include-env
Uploaded by ocramz at 2022-01-08T16:08:15Z
Distributions NixOS:0.3.0.0
Downloads 480 total (44 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Hackage Matrix CI
Docs available [build log]
Last success reported on 2022-01-08 [all 1 reports]

Modules

[Index] [Quick Jump]

Downloads

Maintainer's Corner

For package maintainers and hackage trustees

Candidates


Readme for include-env-0.5.0.0

[back to package description]

include-env

Embed secrets (e.g. API keys) from environment variables inside production artifacts without checking them into the repository.

This use case is relevant e.g. in continuous integration (CI) settings.

Example

In GitHub each private repository can have a number of secrets, which can be conveniently changed without being exposed as needed; GitHub Actions can pass repository secrets in as environment variables during any step, which is where this library comes in handy.