secrets-env

Version, currently 1.2.05 versions

github.com/spider-gazelle/secrets-env

Extension to the crystal lang ENV module to support reading secrets

6 stars
0 dependents
License: MIT

Nothing has been indexed for 1.2.0 yet. The tag is recorded, its shard.yml has not been read, so the manifest and dependency list below are empty because they are unknown rather than because they are absent.

Installation

# Add this to your shard.yml
dependencies:
  secrets-env:
    github: spider-gazelle/secrets-env
    version: ~> 1.2.0

Then run:

shards install

shard.yml

No shard.yml has been indexed for 1.2.0. You can read it on the repository.

Dependencies

Unknown: the shard.yml for this version has not been read yet.

README

This README is the one indexed from the repository at its latest ref, not from the tag for this version.

# secrets-env

Extends the behaviour of the crystal-lang `ENV` module to read values injected by [docker secrets](https://docs.docker.com/engine/swarm/secrets/), [kubernetes secrets](https://kubernetes.io/docs/concepts/configuration/secret/) and other orchestration tools.

## Installation

1. Add the dependency to your `shard.yml`:

   ```yaml
   dependencies:
     secrets-env:
       github: spider-gazelle/secrets-env
   ```

2. Run `shards install`

## Usage

```crystal
require "secrets-env"
```

Use the `SECRETS_PATH` environment variable to specify the volume used for secrets injection.
If unspecified this will default to `/run/secrets`.

`ENV` may then be used as per the standard API.
Values fetch from (in order of priority):
1. environment variable
2. secret of the same name
3. fallback (if specified)

Note: attempts to update the environment (`[]=`) will apply this as an env var.
Secrets are immutable.
Once set as env vars take preference over secrets, the new value is readable by the current machine, but is ephemeral.

Additionally, `ENV.accessed` provides a record of all accesses to the `ENV` variable across the program.