catalog-backend: add Locations to the set of default allowed kinds

docs/features/software-catalog/configuration.md

@@ -23,16 +23,16 @@ configuration.
 ## Catalog Rules
 
 By default the catalog will only allow ingestion of entities with the kind
-`Component` and `API`. In order to allow entities of other kinds to be added,
-you need to add rules to the catalog. Rules are added either in a separate
-`catalog.rules` key, or added to statically configured locations.
+`Component`, `API` and `Location`. In order to allow entities of other kinds to
+be added, you need to add rules to the catalog. Rules are added either in a
+separate `catalog.rules` key, or added to statically configured locations.
 
 For example, given the following configuration:
 
 ```yaml
 catalog:
   rules:
-    - allow: [Component, API, Template]
+    - allow: [Component, API, Location, Template]
 
   locations:
     - type: github
@@ -41,13 +41,13 @@ catalog:
         - allow: [Group]
 ```
 
-We are able to add entities of kind `Component`, `API`, or `Template` from any
-location, and `Group` entities from the `org-data.yaml`, which will also be read
-as statically configured location.
+We are able to add entities of kind `Component`, `API`, `Location`, or
+`Template` from any location, and `Group` entities from the `org-data.yaml`,
+which will also be read as statically configured location.
 
 Note that if the `catalog.rules` key is present it will replace the default
-value, meaning that you need to add rules for `Component` and `API` kinds if you
-want those to be allowed.
+value, meaning that you need to add rules for the default kinds if you want
+those to still be allowed.
 
 The following configuration will reject any kind of entities from being added to
 the catalog: