catalogsource: update dir name (#294)

Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
operator-framework · Sep 7, 2023 · bb012a3 · bb012a3
1 parent 039d150
commit bb012a3
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 7 deletions.
diff --git a/crds/operators.coreos.com_catalogsources.yaml b/crds/operators.coreos.com_catalogsources.yaml
@@ -535,14 +535,12 @@ spec:
                     extractContent:
                       description: ExtractContent configures the gRPC catalog Pod to extract catalog metadata from the provided index image and use a well-known version of the `opm` server to expose it. The catalog index image that this CatalogSource is configured to use *must* be using the file-based catalogs in order to utilize this feature.
                       type: object
-                      required:
-                        - configDir
                       properties:
                         cacheDir:
                           description: CacheDir is the directory storing the pre-calculated API cache.
                           type: string
-                        configDir:
-                          description: ConfigDir is the directory storing the file-based catalog contents.
+                        catalogDir:
+                          description: CatalogDir is the directory storing the file-based catalog contents.
                           type: string
                     memoryTarget:
                       description: "MemoryTarget configures the $GOMEMLIMIT value for the gRPC catalog Pod. This is a soft memory limit for the server, which the runtime will attempt to meet but makes no guarantees that it will do so. If this value is set, the Pod will have the following modifications made to the container running the server: - the $GOMEMLIMIT environment variable will be set to this value in bytes - the memory request will be set to this value \n This field should be set if it's desired to reduce the footprint of a catalog server as much as possible, or if a catalog being served is very large and needs more than the default allocation. If your index image has a file- system cache, determine a good approximation for this value by doubling the size of the package cache at /tmp/cache/cache/packages.json in the index image. \n This field is best-effort; if unset, no default will be used and no Pod memory limit or $GOMEMLIMIT value will be set."