Comment 14 for bug 1475091

I believe we can do better and if not that's going to be really dodgy for keystone_trust provider.

If not we' ll have to fish out (best catch call) using the following as a name for Puppet resource:
`trustor_user,trustee_user,project,[roles]`
And we'll have to fetch/convert each sub-field to its ID equivalent.

A the moment, for puppet needs to create a trust it would have to be something like this
  keystone_trust { 'user1,user2,tenant1,['admin','manager']':
      trustor_user => 'user1',
      trustee_user => 'user2',
      project => 'tenant1',
      roles => ['admin', 'manager']
    }

And since many trusts can exist for a same trustor/trustee/project and roles set, we have to guess the first one, hoping they always come in the same order.

For instance:

# openstack trust list -f value
3c5fb6f4fc1c4163b55ae98051d9311c None False 78e22bb71862481dbe8335b4ce4551e8 ac994e5701d644b6a3ac78c9dd1ad04a 24b047f52ff94029923f7f0ea982f03f
cdf0aeb44173473d87ce13ab02e5400f None False 78e22bb71862481dbe8335b4ce4551e8 ac994e5701d644b6a3ac78c9dd1ad04a 24b047f52ff94029923f7f0ea982f03f

# openstack trust show 3c5fb6f4fc1c4163b55ae98051d9311c -f shell
deleted_at="None"
expires_at="None"
id="3c5fb6f4fc1c4163b55ae98051d9311c"
impersonation="False"
project_id="78e22bb71862481dbe8335b4ce4551e8"
redelegation_count="0"
remaining_uses="None"
roles="admin manager"
trustee_user_id="ac994e5701d644b6a3ac78c9dd1ad04a"
trustor_user_id="24b047f52ff94029923f7f0ea982f03f"

# openstack trust show cdf0aeb44173473d87ce13ab02e5400f -f shell
deleted_at="None"
expires_at="None"
id="cdf0aeb44173473d87ce13ab02e5400f"
impersonation="False"
project_id="78e22bb71862481dbe8335b4ce4551e8"
redelegation_count="0"
remaining_uses="None"
roles="admin manager"
trustee_user_id="ac994e5701d644b6a3ac78c9dd1ad04a"
trustor_user_id="24b047f52ff94029923f7f0ea982f03f"