Introduction
By default, Capact stores the state in a form of TypeInstances, that contain static data. The data is stored unencrypted in the same Capact Local Hub database.
However, there are many cases, where static, unencrypted data is not enough. For example, some sensitive data should be stored in a secure way. Or, Helm chart details may quickly become outdated in case of any external change (e.g. upgrade with helm CLI).
That's why Capact introduced storage backends functionality. Storage backend is a service which manages external TypeInstance's value for every resource version, as well as the lockedBy piece of information.
It supports full TypeInstance lifecycle, that is: create, get, update, delete, lock, unlock operations.
Available storage backends​
Currently, we have the following storage backends available:
Each storage backend is installed separately using Capact Actions. See corresponding documents for each storage to learn how to install and configure them.
Development​
To develop your own storage backend, create a gRPC service which implements the storage backend Protocol Buffers schema.
You can use the generated server code for the following languages:
- Go,
- TypeScript (Node.js),
- or generate your own based on the Protocol Buffers schema.