Hybrid testing failed

[agiguere]

I am trying to test with the CAP hybrid profile and it does not work

cds bind -2 cloud-logging
retrieving data from Cloud Foundry...
creating service key cloud-logging-key - please be patient...
Error: Unknown CDS service name for service cloud-logging. Please specify as argument for cds bind.

it create the service key on my SAP Cloud Logging service instance however the CLI failed and I don't know why

please let me know how I can resolve this

thanks

[agiguere]

However if I set the binding manually via the .cdsrc-private.json file, it works as expected

[sjvans]

hi @agiguere

you need to bind service telemetry to cloud-logging. please see With CDS Service and Kind.

[agiguere]

I tried passing the --kind argument to the CLI and it does not work either

cds bind -2 cloud-logging:bas-hybrid-key --kind cloud-logging

I was able to make the binding works by settings up manually like I said, like this (in cdsrc-private)

      "cloud-logging": {
        "binding": {
          "type": "cf",
          "apiEndpoint": "https://api.cf.us10-001.hana.ondemand.com",
          "org": "<my org>",
          "space": "<my space>",
          "instance": "cloud-logging",
          "key": "bas-hybrid-key",
          "resolved": false
        },
        "vcap": {
          "name": "cloud-logging"
        }

not sure who to make it works via the CLI, can you give me an example please?

[agiguere]

@sjvans please see my reply above, thanks!

[sjvans]

hi @agiguere

it should be cds bind telemetry -2 cloud-logging. as there are multiple export backend options, there is no 1:1 link between the requires entry (telemetry) and the service name (cloud-logging). the kind (telemetry-to-cloud-logging), on the other hand, can be matched to the service name (cloud-logging) automatically.

please reopen, if necessary.

best,
sebastian

[agiguere]

@sjvans it works however, if I compare the environment variables between the production profile vs the hybrid profile, they are different, the environment JSON object in production is cloud-logging, same as the VCAP. With your bind command, the JSON object will be named telemetry as well as the VCAP name

another question, what about the CAP development profile, right now I can't use CDS watch because it says credential not found?

thanks

[sjvans]

hi @agiguere

don't mind the difference. the cds bind JSON and the app env JSON have different structures/ contents.

with, --for you can also specify a profile for the binding: https://cap.cloud.sap/docs/advanced/hybrid-testing#with-different-profile

best,
sebastian