What is ConfigStore?
ConfigStore provides way to store: Key, Value, and Metadata information that can be shared across all of your applications.
How does ConfigStore differ from Environment Variables
When you add Environment Variables to your application they will end up as actual Linux Operating System Environment Variables.
ConfigStore records provide an alternative place to store centralised information that will not be exposed in OS level environment variables.
This is most useful for information that you need to access from Kubernetes configuration files. For example within Skycap Stencil Templates.
You can use ConfigStore in your Rails applications if it suites your needs. One example might be a centralised place to store Cloud Account information. You could add these credentials to your account level ConfigStore and then access this data from an environment variable in your applications.
ConfigStore Data Structure
Data edited from within the UI is text only and is structured as:
Key — A text based Key.
Value — A text based Value.
Metadata — A comma separated list of key=value pairs. For example: key1=value1, key2=value2
If you need to store binary data you should use the CLI.
Application level ConfigStore is accessed from the right hand application menu Configuration → ConfigStore tab. This page provides a way to store information where the scope is limited to a specific application.
Account wide ConfigStore is accessed from the Account Settings page → ConfigStore menu item. It provides a way to store information globally that can be referenced by all of by Applications.
Examples of how to Access ConfigStore Variables?
You access ConfigStore data by using the following syntax:
Skycap Stencil Templates