Grpc tests headers definition in yaml

[EGYG33K]

Hi everyone,
First of all thank you for the cool tool. I have a problem as my gRPC tests require headers and i tried to define them in the metadata section like

version: "1.0"
name: gRPC service template
env:
  host: localhost:9090
  tenant: tenant1
tests:
  example:
    name: Employees tests
    continueOnFail: true
    steps:
      - name: Get Employee by last name
        grpc:
          proto:
            - public/EmployeeService.proto
          host: ${{env.host}}
          service: com.atoss.template.servicetemplate.adapter.handler.grpc.employee.v1.EmployeeService
          method: getEmployeesByLastName
          metadata:
            - X-Tenant-ID: tenant1
          data:
            lastName: Babanu
          headers:
            X-Tenant-ID: {{env.tenant}}
          check:
            jsonpath:
              $.firstName: "Fane"

But the header is not sent with the request. I was just wondering if stepci support defining headers for gRPC calls or maybe there is something wrong on my definition. Thank you in advance.

Best regards,
Samy

[mishushakov]

Have you tried this?

version: "1.0"
name: gRPC service template
env:
  host: localhost:9090
  tenant: tenant1
tests:
  example:
    name: Employees tests
    continueOnFail: true
    steps:
      - name: Get Employee by last name
        grpc:
          proto:
            - public/EmployeeService.proto
          host: ${{env.host}}
          service: com.atoss.template.servicetemplate.adapter.handler.grpc.employee.v1.EmployeeService
          method: getEmployeesByLastName
          metadata:
            X-Tenant-ID: tenant1
          data:
            lastName: Babanu
          check:
            jsonpath:
              $.firstName: "Fane"

[EGYG33K]

Yep i tried that as well but same result. I used the grpc-dump to see what goes in the request but the metadata wasn't in the request.

[mishushakov]

When you use a regular client (eg. Postman, Insomnia) does your server handle the metadata correctly?

[EGYG33K]

Yep it works fine with postman and kreya and other gRPC clients

[EGYG33K]

Below is the list of the metadata i get
grpc-accept-encoding=identity,deflate,gzip
accept-encoding=identity
user-agent=grpc-node-js/1.8.7
content-type=application/grpc
But my defined metadata doesn't come along for some reason

[mishushakov]

Alright, will look into it and let you know once I have anything
Thank you 🙏

[EGYG33K]

Hi @mishushakov, Did you find some time to look at this? We would like to use StepCI and this is the only point that preventing us from doing that.

[mishushakov]

Thanks for the reminder. Sorry it took so long. Currently we're very busy, but we will be looking into it

[boozilla]

I'm having the same problem

[mishushakov]

Fixed in the latest release of cool-grpc 1.1.6

Please update your dependencies 😉

[sebastianwis]

Hey Amr @EGYG33K and @boozilla
Thank you for your report here!
It would be amazing to welcome you to our Discord if you haven't joined it yet:
https://discord.com/invite/KqJJzJ3BTu
This is where we keep users up to date with updates, features and bug resolutions.