role_user_assignments

Use this endpoint to give a user permission to a resource or an organization. The needed data is the user, the role definition, and the object id. The object must be of the type specified in the role definition. The type given in the role definition and the provided object_id are used to look up the resource.

After creation, the assignment cannot be edited, but can be deleted to remove those permissions.

get/role_user_assignments/

Query parameters

pageinteger

A page number within the paginated result set.

page_sizeinteger

Number of results to return per page.

searchstring

A search term.

Response

countinteger
nextstring uri nullable
previousstring uri nullable
page_sizeinteger nullable
pageinteger nullable

Example response

{
  "count": 123,
  "next": "/eda/api/v1/example/?page=51&page_size=100",
  "previous": "/eda/api/v1/example/?page=49&page_size=100",
  "page_size": 100,
  "page": 50
}

Changes

Changed in 4 of the 8 revisions of this API.313

  • c04fc5f09692211See the full diff
    • the response property results/items/object_ansible_id became nullable for the status 200

      response-property-became-nullable

    • the response property results/items/user_ansible_id became nullable for the status 200

      response-property-became-nullable

    • added the new eda.eventstream enum value to the results/items/content_type/allOf[ContentTypeEnum]/ response property for the response status 200

      response-property-enum-value-added

    • removed the eda.credentialtype enum value from the results/items/content_type/allOf[ContentTypeEnum]/ response property for the response status 200

      response-property-enum-value-removed

    This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

    • removed the eda.extravar enum value from the results/items/content_type/allOf[ContentTypeEnum]/ response property for the response status 200

      response-property-enum-value-removed

    This revision also has 4 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

    • endpoint added

      endpoint-added

    This revision also has 24 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

    • api path removed without deprecation

      api-path-removed-without-deprecation

    This revision also has 64 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog