Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

protobuf files in the extra volumes #56

Open
Demmyart opened this issue Nov 20, 2023 · 1 comment
Open

protobuf files in the extra volumes #56

Demmyart opened this issue Nov 20, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@Demmyart
Copy link

Hi, I'm trying to use the processor as follows:

    #   processors:
    #     - protobuf:
    #         operator: to_json
    #         message: FillReport
    #         import_paths: [ protobuf ]

So, I have configmap which is mounted as a volume then:

  extraVolumes: 
    - name: proto-vol
      configMap:
        name: protobuf

  extraVolumeMounts:
    - name: proto-vol
      mountPath: /protobuf

And after that I'm getting the following error:
level=error msg="Failed to create stream (fill_report_stream): failed to init processor <no label> path root.pipeline.processors.0: ..2023_11_20_13_23_29.2531302976/FillReport.proto:4:9: symbol \"FillReport\" already defined at FillReport.proto:4:9" @service=benthos

Inside of the container, I'm getting the folder structure with multiple links:

45341956 drwxr-xr-x    2 root     root            30 Nov 20 20:01 ..2023_11_20_20_01_05.1721020983
43088997 lrwxrwxrwx    1 root     root            32 Nov 20 20:01 ..data -> ..2023_11_20_20_01_05.1721020983
43089266 lrwxrwxrwx    1 root     root            23 Nov 20 20:01 FillReport.proto -> ..data/FillReport.proto

Should we actually do this manipulation? What should I do to pass my proto file to the processor?

@charlie-haley charlie-haley added the bug Something isn't working label Dec 8, 2023
@charlie-haley
Copy link
Collaborator

There shouldn't be anything in the chart that's doing this manipulation, extraVolumes and extraVolumeMounts just map to volumes and volumeMounts on the Deployment itself.

What does the ConfigMap you're using look like?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants