Fast Data Secrets Resolution

Fast Data services may have secrets inside their Config Maps. Secrets can be injected as:

• plain text
• reference to an environment variable
• reference to a file, either its full content or the internal key of a .ini file

These are the services versions that support this feature in their config maps:

Control Plane	Projection Storer	Real Time Updater	Single View Trigger Generator	Single View Creator
>=1.1.0	>=1.2.0	-	>=3.3.1	-

Plain Text

The field is set to be a string and it is loaded directly from the Config Map itself.

{
  "some-entry": {
    // ...,
    "some-secret-field": {
      "url": "{{CONNECTION_STRING}}"
    }
  }
}

danger

Remember to use external environment variables, to avoid store them in plain in your Console configuration!

Environment Variable

The field is populated by a microservice environment variable.

{
  "some-entry": {
    // ...,
    "some-secret-field": {
      "url": {
        "type": "env",
        "key": "<ENVIRONMENT VARIABLE NAME>"
      }
    }
  }
}

tip

By default the value contained in the environment variable that is referenced within the secret is expected to be a plain text. However, the secret definition allows to define the encoding property to base64, so that the value contained in the environment variable can be written in base64 format.

{
  "some-entry": {
    // ...,
    "some-secret-field": {
      "url": {
        "type": "env",
        "key": "<ENVIRONMENT VARIABLE NAME>",
        "encoding": "base64"
      }
    }
  }
}

File Reference

The field is populated by the content of a file mounted inside the microservice.

Full Content

{
  "some-entry": {
    // ...
    "some-secret-field": {
      "url": {
        "type": "file",
        "path": "/path/to/file"
      }
    }
  }
}

.ini Key

If the chosen file is a .ini file with key-value pair values, it's possible to specify a key that needs to be interpolated.

{
  "some-entry": {
    // ...
    "some-secret-field": {
      "url": {
        "type": "file",
        "path": "/path/to/file.ini",
        "key": "<KEY NAME>"
      }
    }
  }
}