Pass Iglu API key to Snowplow Micro in iglu.json

Hi there,

We’re using Snowplow Micro to test events being sent and all works well. :slight_smile: However, we want to send an API key for the connection to our Iglu Server but keep the key as an environment variable. Our iglu.json looks something like this:

  "schema": "iglu:com.snowplowanalytics.iglu/resolver-config/jsonschema/1-0-1",
    "data": {
      "cacheSize": 5000,
      "repositories": [
          "name": "Iglu Central",
          "priority": 0,
          "vendorPrefixes": [ "com.snowplowanalytics" ],
          "connection": {
            "http": {
              "uri": ""
          "name": "***",
          "priority": 5,
          "vendorPrefixes": [ "***" ],
          "connection": {
            "http": {
              "uri": "***",
              "apikey": "DON'T WANT TO COMMIT API KEY"

Adding the API key to iglu.json works but we don’t want to commit that to Git. Is there a way, when passing iglu.json to Snowplow Micro, that we can pass the API key separately? Something like:

docker run \
  --mount type=bind,source=$(pwd)/example,destination=/config \
  -p 9090:9090 \
  snowplow/snowplow-micro:1.2.1 \
  --collector-config /config/micro.conf \
  --iglu /config/iglu.json \

Hopefully I’ve got all the terminology right. :smiley:

Thanks in advance,

Hi @Robert_Douglas
Welcome to the Snowplow Community!

Hi @Robert_Douglas, no it is not possible to pass the api key separately from the iglu resolver file.

It makes me quite sad that that’s my answer for you! Especially as many Snowplow configuration files do let you set any parameter using an environment variable at run time, e.g. this example for Iglu Server. Unfortunately this configuration method has not been extended to Iglu resolver files yet.

1 Like

Okay, thanks anyway. We’ll work around it. :slight_smile: