Closed Tomcli closed 6 years ago
We'll see since it is still deploying, but I get this error early in the deploy (which I also got previously):
Hmm, is your build stage pulling the latest commit?
looks like it is:
Hmm it works for me. Anyway, I will work on a create_classifier() function in case anyone can't get their API KEY using the cf command
It might be something with the VizRec service. They recycle API keys, so whenever you start a new service you get the same key. Perhaps there's something going on when the toolchain provisions the new service and gets the credential. I've had a similar problem with Watson Natural Language Classifier, and I still haven't solved it. maybe you could put some debug code to print out the api key it gets. It seems I looked at it one of these Deploys, and it was different from the recycled one I keep getting.
Note that I am not using cf to get the API key. I'm using the Deploy to IBM Cloud
button.
Perhaps you can try the Deploy to IBM Cloud
button and see if that works for you?
Yeah, the Deploy to IBM Cloud
button use a script that call cf command to get the API KEY
and the Deploy to IBM Cloud
button works on my account
I believe the API KEY under VCAP_SERVICE should always be correct. I will add a condition in the server to create a new waste model when it's not exist.
I don't think there's anything wrong with your code, I think there's a race condition in the deploy pipeline. I might test a couple things in a forked repo. In the mean time, I think we can move on.
The --guid flag no longer return the correct API KEY for visual recognition. Thus Updating the command to parse with awk.
Also adding CLI reference for viewing model status.