Lint error with GRPC plugin: unable to infer component type
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Reproduce the report with redpanda-connect lint --skip-env-var-check benthos/... and the shown custom plugin paths. Start by tracing how benthos/plugins/myplugin/plugin.yaml is parsed and how benthos/resources/common.yaml infers the component type. Done means the custom gRPC plugin configuration can be linted without the reported field or component-type errors.
Written by the indexing model from the issue text.
Description
Hi.
I tried to lint config which uses custom golang plugin.
$ redpanda-connect lint --skip-env-var-check benthos/...
benthos/plugins/myplugin/plugin.yaml(1,1) field name not recognised
benthos/plugins/myplugin/plugin.yaml(2,1) field summary not recognised
benthos/plugins/myplugin/plugin.yaml(3,1) field command not recognised
benthos/plugins/myplugin/plugin.yaml(4,1) field type not recognised
benthos/plugins/myplugin/plugin.yaml(5,1) field fields not recognised
benthos/resources/common.yaml(38,1) unable to infer component type: [label myplugin]
How can I avoid this error?
I can move plugins directory but benthos/resources/common.yaml will still result in an errorr.
- Dominant language
- Go
- Stars
- 571
- Forks
- 121
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 17
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from redpanda-data/benthos
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
redpanda-data/benthos#404 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
redpanda-data/benthos#503 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
redpanda-data/benthos#502 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 72/100
redpanda-data/benthos#481 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
redpanda-data/benthos#469 ·
Maintainers usually reply within 1 day
All issues in redpanda-data/benthos
Similar issues
-
area/proxy kind/bug priority/backlog triage/accepted
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
lexfrei/cloudflare-tunnel-gateway-controller#840 ·
Maintainers usually reply within 1 day
-
area:chat bug sev:papercut
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Agent-Field/CodeAF#1592 ·
Maintainers usually reply within 1 day
-
kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 7 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug P2 reliability
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
afreidah/s3-orchestrator#1564 ·
Maintainers usually reply within 1 day