Can not provision IBM service with a service id

[ibm]

Can not provision IBM service with a service id

[vazirim]

Fixed in v0.1.6

[qibobo]

Seems the similar issue in terraform-provider-ibm IBM-Cloud/terraform-provider-ibm#591
The root cause is the old version of bluemix-go.

[dwakeman]

I need to be able to use service IDs as well, and I am very interested in the resolution of this issue.

Thanks!

[qibobo]

@vazirim
Any updates?

[vazirim]

@qibobo I am unable to reproduce this problem. It works for me.
Can you please retry and see if you still have the problem (it could be that bluemix was not cooperating when you last tried this)?

@dwakeman Did you try using a serviceid and it didn't work?

[dwakeman]

No, just happened to be viewing the issues list and saw this. I will test it out.

[vazirim]

All you need is for your seed-secret to contain the api-key of the serviceId, and to give it proper access permissions in iam.

[qibobo]

@vazirim
When I used the latest version(v1.0.5), I still can not provision service successfully. Now the error is Request failed with status code: 400, ServerErrorResponse: {"message":"The resource group 0000161cdb364e489a09f7f971a34363 is inactive with state: SUSPENDED","status_code":400,"transaction_id":"bss-5a2dc634bdce8422"}
I have tried serval times and it always failed with the same error.

And I have manually checked my service id could provision service.

[vazirim]

The latest release does not address this issue.

That is also the error that I see. I have been looking at the ibmcloud cli to see what they are doing differently. They are using a different library for starters (ibmcloud-cli-sdk) instead of bluemixgo. In the long run we need to understand which library to use. In the shorter term, I will try to find out what REST calls need to happen on IAM and do those directly, bypassing bluemixgo. Please don't expect a rapid fix for this.

[qibobo]

It works now. Thank you!