Local Storage binding spec
Detailed documentation on the Local Storage binding component
Component format
To set up the Local Storage binding, create a component of type bindings.localstorage
. See this guide on how to create and apply a binding configuration.
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: <NAME>
spec:
type: bindings.localstorage
version: v1
metadata:
- name: rootPath
value: <string>
Spec metadata fields
Field | Required | Binding support | Details | Example |
---|---|---|---|---|
rootPath | Y | Input / Output | The root path anchor to which files can be read / saved | “/temp/files” |
Binding support
This component supports output binding with the following operations:
create
: Create fileget
: Get filelist
: List filesdelete
: Delete file
Create file
To perform a create file operation, invoke the Local Storage binding with a POST
method and the following JSON body:
Note: by default, a random UUID is generated. See below for Metadata support to set the name
{
"operation": "create",
"data": "YOUR_CONTENT"
}
Examples
Save text to a random generated UUID file
On Windows, utilize cmd prompt (PowerShell has different escaping mechanism)
curl -d "{ \"operation\": \"create\", \"data\": \"Hello World\" }" http://localhost:<dapr-port>/v1.0/bindings/<binding-name>
curl -d '{ "operation": "create", "data": "Hello World" }' \
http://localhost:<dapr-port>/v1.0/bindings/<binding-name>
Save text to a specific file
curl -d "{ \"operation\": \"create\", \"data\": \"Hello World\", \"metadata\": { \"fileName\": \"my-test-file.txt\" } }" \
http://localhost:<dapr-port>/v1.0/bindings/<binding-name>
curl -d '{ "operation": "create", "data": "Hello World", "metadata": { "fileName": "my-test-file.txt" } }' \
http://localhost:<dapr-port>/v1.0/bindings/<binding-name>
Save a binary file
To upload a file, encode it as Base64. The binding should automatically detect the Base64 encoding.
curl -d "{ \"operation\": \"create\", \"data\": \"YOUR_BASE_64_CONTENT\", \"metadata\": { \"fileName\": \"my-test-file.jpg\" } }" http://localhost:<dapr-port>/v1.0/bindings/<binding-name>
curl -d '{ "operation": "create", "data": "YOUR_BASE_64_CONTENT", "metadata": { "fileName": "my-test-file.jpg" } }' \
http://localhost:<dapr-port>/v1.0/bindings/<binding-name>
Response
The response body will contain the following JSON:
{
"fileName": "<filename>"
}
Get file
To perform a get file operation, invoke the Local Storage binding with a POST
method and the following JSON body:
{
"operation": "get",
"metadata": {
"fileName": "myfile"
}
}
Example
curl -d '{ \"operation\": \"get\", \"metadata\": { \"fileName\": \"myfile\" }}' http://localhost:<dapr-port>/v1.0/bindings/<binding-name>
curl -d '{ "operation": "get", "metadata": { "fileName": "myfile" }}' \
http://localhost:<dapr-port>/v1.0/bindings/<binding-name>
Response
The response body contains the value stored in the file.
List files
To perform a list files operation, invoke the Local Storage binding with a POST
method and the following JSON body:
{
"operation": "list"
}
If you only want to list the files beneath a particular directory below the rootPath
, specify the relative directory name as the fileName
in the metadata.
{
"operation": "list",
"metadata": {
"fileName": "my/cool/directory"
}
}
Example
curl -d '{ \"operation\": \"list\", \"metadata\": { \"fileName\": \"my/cool/directory\" }}' http://localhost:<dapr-port>/v1.0/bindings/<binding-name>
curl -d '{ "operation": "list", "metadata": { "fileName": "my/cool/directory" }}' \
http://localhost:<dapr-port>/v1.0/bindings/<binding-name>
Response
The response is a JSON array of file names.
Delete file
To perform a delete file operation, invoke the Local Storage binding with a POST
method and the following JSON body:
{
"operation": "delete",
"metadata": {
"fileName": "myfile"
}
}
Example
curl -d '{ \"operation\": \"delete\", \"metadata\": { \"fileName\": \"myfile\" }}' http://localhost:<dapr-port>/v1.0/bindings/<binding-name>
curl -d '{ "operation": "delete", "metadata": { "fileName": "myfile" }}' \
http://localhost:<dapr-port>/v1.0/bindings/<binding-name>
Response
An HTTP 204 (No Content) and empty body will be returned if successful.
Metadata information
By default the Local Storage output binding auto generates a UUID as the file name. It is configurable in the metadata property of the message.
{
"data": "file content",
"metadata": {
"fileName": "filename.txt"
},
"operation": "create"
}
Related links
- Basic schema for a Dapr component
- Bindings building block
- How-To: Trigger application with input binding
- How-To: Use bindings to interface with external resources
- Bindings API reference
Last modified June 19, 2023: Merge pull request #3565 from dapr/aacrawfi/skip-secrets-close (b1763bf)