In the scenario where a user has multiple object stores or buckets, they'll likely want to look up the credentials for their object store in Bluemix. However, the credentials found in the "Service Credentials" tab aren't exactly what you need.
Currently, Service Credentials for "Cloud Object Storage" look like:
We could reduce this overhead to the user in this library by allowing for the service_credentials_from_bluemix to be passed in at instantiation. The ibmos2spark library could detect these are bluemix creds and then perform the appropriate requests and string splicing to get the needed values.
On the other hand, this might be too much overhead to maintain compatibility with they way that Bluemix presents the credentails.
In the scenario where a user has multiple object stores or buckets, they'll likely want to look up the credentials for their object store in Bluemix. However, the credentials found in the "Service Credentials" tab aren't exactly what you need.
Currently, Service Credentials for "Cloud Object Storage" look like:
In order to get the correct set of credentials to use the 'api_key' auth, one must:
We could reduce this overhead to the user in this library by allowing for the
service_credentials_from_bluemix
to be passed in at instantiation. Theibmos2spark
library could detect these are bluemix creds and then perform the appropriate requests and string splicing to get the needed values.On the other hand, this might be too much overhead to maintain compatibility with they way that Bluemix presents the credentails.