Deletes the persisted data from the storage backend. Not all storage backends support deletion.
The key to use to delete the data from the storage backend. The key is implementation specific and might be a file path, a config map name, or an environment variable prefix.
Checks if the storage backend supports the given operation. Implementations must provide a valid definition which responds appropriately for the requested operation.
The desired storage operation to check.
True if the operation is supported, false otherwise.
List all keys in the storage backend. Not all storage backends support listing keys.
A list of keys in the storage backend.
Reads the persisted data from the storage backend and marshals it into bytes.
The key to use to read the data from the storage backend. The key is implementation specific and might be a file path, a config map name, or an environment variable prefix.
The persisted data represented as a byte array.
Write the configuration data to the storage backend by marshalling the bytes into the underlying persistent data format.
The key to use to write the data to the storage backend. The key is implementation specific and might be a file path, a config map name, or an environment variable prefix.
The persistent data represented as a byte array.
The storage backend implementations provide the logic to read and write configuration and other persistent data layer elements to and from various storage mediums.
The Data Layer API must provide the following minimal set of implementations:
Storage backends should not attempt to interpret or validate the data being read or written, but should handle the conversion of plain javascript objects to the underlying data format and vice versa.