A ConfigStore is a storage system for Configs, which can be any system or service that is capable of storing data. This can include text files, databases, secret managers, and Configu's SaaS Configuration Store. ConfigStores are responsible for storing, retrieving, and managing configuration data, and developers can choose the ConfigStore that best fits their needs and workflow.

ConfigStores are unique in their type, and can be referenced as instances of their class implementation when using Configu's SDK. When using Configu's CLI, ConfigStores are referenced using connection strings, which can also be cached as short labels for convenience.

Configu's interfaces support a wide range of ConfigStores and are open source, so if you don't see a ConfigStore that meets your needs, you can easily create your own by implementing a simple abstract class with get and set methods. This allows you to extend Configu to fit your specific configuration management needs.

Here are some examples of using Configu SaaS Store with Configu's CLI:

configu store upsert --label "my-store" --interactive

configu store upsert -l "my-store" --connection-string "store=configu;org=my-company;token=123abc;type=Token"

configu store upsert --type "configu"

configu store list

configu [COMMAND] --store "my-store" ...
configu [COMMAND] --store "store=configu;org=my-company;token=123abc;type=Token" ...

configu store delete -l "my-store"

Supported stores:

  • Configu SaaS Store
  • Files:
    • JSON
  • Secret managers:
    • HashiCorp Vault
    • AWS Secrets Manager
    • Azure Key Vault
    • Google Secret Manager
    • Kubernetes Secret
  • Databases:
    • MySQL
    • Microsoft SQL server
    • SQLite
    • PostgreSQL
    • CockroachDB
    • MariaDB
    • Amazon Aurora
  • Browser:
    • LocalForage