We haven't added a feature yet that lets you associate more than one cloud connection with a deployment. That's simple a feature that needs to be there, but isn't yet. As a workaround, you can insert the provider info including credentials etc to the template directly. The starter packs we have for multi-cloud deployments show what that might look like:
"provider": {
"aws": {
"access_key": "${var.aws_access_key}",
"secret_key": "${var.aws_secret_key}",
"region": "${var.aws_region}"
},
"ibmcloud": {
}
},
The sample above adds concrete AWS data to the template while leaving the IBM Cloud one empty, meaning you pick the IBM Cloud connection at deployment time. Again, this is just a temporary workaround.