anchor.diff:  }
   --------------------------------------------------
   // CONSOLE
  -<1> Mappings that have `enabled` set to `false` will be ignored when role-mapping
  +<1> Mappings that have `enabled` set to `false` will be ignored when role mapping
       is performed.
   <2> Metadata is optional
  -
  -The `roles`, `enabled`, and `rules` fields are required at the top-level.
  -Within the `metadata` object, keys beginning with `_` are reserved for system
  -usage.
   
   A successful call returns a JSON structure that shows whether the mapping has
   been created or updated.
  
positive.code: [[security-api-role-mapping]]
  === Role Mapping APIs
  
  The Role Mapping API enables you to add, remove, and retrieve role-mappings.
  To use this API, you must have at least the `manage_security` cluster privilege.
  
  NOTE: The API requires that each role-mapping have a distinct name. The name is
   used solely as an identifier to facilitate interaction via the API, and does
   not affect the behavior of the mapping in any way.
  
  [[security-api-put-role-mapping]]
  To add a role-mapping, submit a PUT or POST request to the `/_xpack/security/role_mapping/<name>`
  endpoint:
  
  [source,js]
  
negative.code: // TEST[continued]
  
  [[security-api-delete-role-mapping]]
  To delete a role mapping, submit a DELETE request to the
  `/_xpack/security/role_mapping/<name>` endpoint:
  
  [source,js]
  