on 2022 Oct 05 4:14 AM
Hi,
We are currently experiencing an issue when trying to run our CAP service through hybrid testing. The weird thing is that everything was fine yesterday. The issue just started today.
// Fails for some reason in BAS
cds bind -2 service:service-key
// Also fails for some reason in BAS, also mentioning the live reload port error
cds watch --profile hybrid
Everything works fine in VS Code though:
Stopping / starting the dev space doesn't seem to help as well.
Is there an ongoing issue with BAS? Hoping for some clarity on this issue.
Thanks!
John
Request clarification before answering.
Seems to only affect hybrid testing using "cds bind". It fails to resolve the bindings due to some issue with BAS or something.
As a workaround, I went with using the old "default-env.json" way of testing and was able to execute "cds watch --profile hybrid".
Hope they can fix this issue soon though. Having to constantly update VCAP services after every deployment is such a hassle.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanky John this worked well. I just copied the VCAP_SERVICES part into default-env.json and Im now able to work with cds-watch.
That's great Matteo. Glad it worked. Note that sometimes, deploying the app invalidates the credentials you extracted via the VCAP_SERVICES so you would have to get a fresh copy from Environment Variables again. 🙂
But yes, hopefully someone from SAP can help us. CDS Bind is still the most convenient way to perform Hybrid Testing.
User | Count |
---|---|
49 | |
10 | |
8 | |
6 | |
5 | |
5 | |
4 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.