This is an automated email from the ASF dual-hosted git repository.
eamonford pushed a commit to branch bug_fixes
in repository https://gitbox.apache.org/repos/asf/incubator-sdap-nexus.git
The following commit(s) were added to refs/heads/bug_fixes by this push:
new fe3297f Readme
fe3297f is described below
commit fe3297f627bc85aac457f445c0a82675040488b9
Author: Eamon Ford <[email protected]>
AuthorDate: Mon Dec 7 14:34:19 2020 -0600
Readme
---
helm/README.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/helm/README.md b/helm/README.md
index be86fd5..aeb15d8 100644
--- a/helm/README.md
+++ b/helm/README.md
@@ -250,7 +250,9 @@ See the [nginx-ingress Helm chart
docs](https://github.com/helm/charts/tree/mast
## The Collections Config
In order to ingest data into SDAP, you must write a Collections Config. This
is a YAML-formatted configuration which defines
-what granules to ingest into which collections (or "datasets"), and how. There
are two ways to manage the Collections Config:
+what granules to ingest into which collections (or "datasets"), and how. See
the [Collections Manager
docs](https://github.com/apache/incubator-sdap-ingester/tree/dev/collection_manager#the-collections-configuration-file)
for information on the proper content and format of the Collections Config.
+
+There are two ways to manage the Collections Config:
### Option 1: Manually Create a ConfigMap
Create a
[ConfigMap](https://kubernetes.io/docs/concepts/configuration/configmap/) by
hand, containing the collections config YAML under a key called
`collections.yml`. Then set the Chart configuration option
`ingestion.collections.configMap` to the name of the ConfigMap.
