keystone_user_role provider should be `domain` aware

Bug #1488538 reported by Vasyl Saienko
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
puppet-keystone
Fix Released
Undecided
Richard Megginson

Bug Description

With keystone V3 API and multidomains support `user_name` attribute is no longer globally unique. It is rather `domain` unique .
keystone_user_role should receive `domain_name` and `user_name` in order to clearly define user.

Tags: multidomains
Vasyl Saienko (vsaienko)
Changed in puppet-keystone:
assignee: nobody → Vasyl Saienko (vsaienko)
Vasyl Saienko (vsaienko)
tags: added: multidomains
Revision history for this message
Richard Megginson (rmeggins) wrote :

This is already supported with the current code. You specify it like this::

    keystone_user_role { 'username::user_domain_name@projectname::project_domain_name': }

This assumes you have the following resources defined in your manifest::

    keystone_tenant { 'projectname::project_domain_name': ...}
    keystone_user { 'username::user_domain_name': ...}

Changed in puppet-keystone:
assignee: Vasyl Saienko (vsaienko) → Richard Megginson (rmeggins)
status: New → Fix Released
Matt Fischer (mfisch)
Changed in puppet-keystone:
milestone: none → 7.0.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.