dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update daprdocs/content/en/operations/components/pluggable-components-registration.md 

Co-authored-by: Phillip Hoff <phillip@orst.edu>
Signed-off-by: Tiago Alves Macambira <tmacam@burocrata.org>
This commit is contained in:
Tiago Alves Macambira 2023-02-08 15:27:53 -08:00 committed by GitHub
parent 41fd252e76
commit e5b36e2c1c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
daprdocs/content/en/operations/components/pluggable-components-registration.md
View File

@ -68,7 +68,7 @@ Define your component using a [component spec]({{< ref component-schema.md >}}).
You will need to define one [component spec]({{< ref component-schema.md >}}) for each building block exposed by your pluggable component's [Unix Domain Socket][uds]. From the example above, the UDS `my-component.sock` from the previous example, exposes a pluggable component named `my-component` with both a `state` and a `pubsub` building blocks. Two components specs, each in their own YAML file placed in the resouces-path, will be required, one for `state.my-component` and another for `pubsub.my-component`.
For instance, the component spec for `state.my-component` could be as follow
For instance, the component spec for `state.my-component` could be:
```yaml
apiVersion: dapr.io/v1alpha1