Add comments inadvertently removed during migrate (#27)

A few files had their first comment removed even though it did not
contain a license. This re-adds those comments.

Author: hub-cap

x-pack/plugin/security/src/main/config/role_mapping.yml

@@ -0,0 +1,14 @@
+# Role mapping configuration file which has elasticsearch roles as keys
+# that map to one or more user or group distinguished names
+
+#roleA:   this is an elasticsearch role
+#  - groupA-DN  this is a group distinguished name
+#  - groupB-DN
+#  - user1-DN   this is the full user distinguished name
+
+#power_user:
+#  - "cn=admins,dc=example,dc=com"
+#user:
+#  - "cn=users,dc=example,dc=com"
+#  - "cn=admins,dc=example,dc=com"
+#  - "cn=John Doe,cn=other users,dc=example,dc=com"

x-pack/plugin/security/src/main/config/roles.yml

@@ -0,0 +1,3 @@
+# The default roles file is empty as the preferred method of defining roles is
+# through the API/UI. File based roles are useful in error scenarios when the
+# API based roles may not be available.

x-pack/plugin/security/src/test/resources/org/elasticsearch/xpack/security/authc/ldap/role_mapping.yml

@@ -1,3 +1,4 @@
+# AD Realm Role Mapping
 group_role:
   - "CN=Avengers,CN=users,DC=ad,DC=test,DC=elasticsearch,DC=com"
 user_role:

x-pack/plugin/security/src/test/resources/org/elasticsearch/xpack/security/authc/ldap/support/ldapWithGroupSearch.yml

@@ -1,3 +1,4 @@
+# This LDAP connection does group lookup by a subtree search, no role mapping
 ldap:
   urls:
     - ldap://ldap.example.com:1389

x-pack/plugin/security/src/test/resources/org/elasticsearch/xpack/security/authc/ldap/support/ldapWithRoleMapping.yml

@@ -1,3 +1,4 @@
+# This LDAP connection does group lookup by attribute with group to role mapping
 ldap:
   urls: # these connections are not round-robin, but primary, secondary, etc.  When the first fails the second is attempted
     - ldap://ldap.example.com:1389

x-pack/plugin/security/src/test/resources/org/elasticsearch/xpack/security/authc/pki/role_mapping.yml

@@ -1,2 +1,4 @@
+# Role mappings for PKI tests
+
 user:
   - "CN=Elasticsearch Test Node, OU=elasticsearch, O=org"

x-pack/plugin/security/src/test/resources/org/elasticsearch/xpack/security/authc/support/role_mapping.yml

@@ -1,3 +1,9 @@
+# roleA   this is an elasticsearch role
+#  - groupA-DN  this is any group, ldap DN, or unix group
+#  - groupB-DN
+#  - user1-DN
+
+#This is an example of ldap mapping configuration
 security:
   - "cn=avengers,ou=marvel,o=superheros"
   - "cn=shield,ou=marvel,o=superheros"

x-pack/plugin/security/src/test/resources/org/elasticsearch/xpack/security/authz/store/default_roles.yml

@@ -0,0 +1,3 @@
+# The default roles file is empty as the preferred method of defining roles is
+# through the API/UI. File based roles are useful in error scenarios when the
+# API based roles may not be available.

x-pack/plugin/security/src/test/resources/org/elasticsearch/xpack/security/authz/store/reserved_roles.yml

@@ -1,3 +1,5 @@
+# All cluster rights
+# All operations on all indices
 admin:
   cluster:
     - all

x-pack/plugin/src/test/resources/rest-api-spec/test/xpack/10_basic.yml

@@ -1,3 +1,5 @@
+# Integration tests for monitoring
+#
 "X-Pack loaded":
     - do:
         cluster.state: {}