Kavitha Thulasiraman
--- a/docs/developer/package-integration/package-integration-storage.md

+ 8

− 21
+++ b/docs/developer/package-integration/package-integration-storage.md

+ 8

− 21
 @@ -8,7+8,7 @@

 Addon Minio is enabled at the BigBang level. Alternatively, you have (1) an existing Minio Instance, (2) an AWS S3 AccessKey and SecretKey, or (3) an existing S3 bucket for the deployment.

 ## Integration

 There are currently 2 typical ways in bigbang that packages connect to object storage.

 @@ -62,7+62,7 @@

 - add a conditional statement to `bigbang/chart/templates/<package>/values` that will check if the object storage values exist and creates the necessary <TODO> values.

-  If object storage values are present, then the internal object storage is disabled by setting `enabled: false` and the server, database, username, and port values are set. <TODO>
+  If object storage values are present, then the internal object storage is disabled by setting `enabled: false` and the endpoint, accessKey, accessSecret, and bucket values are set. 

-  If object storage values are NOT present then the internal database is enabled and default values declared in the package are used.
+  If object storage values are NOT present then the minio cluster is enabled and default values declared in the package are used.

 ```yml
 {{- if .Values.addons.gitlab.objectStorage.endpoint }}
 @@ -76,13 +76,14 @@ task-runner:
        key: backups
 {{- end }}
 ```
-Example: [GitLab](https://repo1.dso.mil/platform-one/big-bang/bigbang/-/blob/10d43bea9351b91dfc6f14d3b0c2b2a60fe60c6a/chart/templates/gitlab/values.yaml#L49)
+Example: [GitLab](https://repo1.dso.mil/platform-one/big-bang/bigbang/-/blob/10d43bea9351b91dfc6f14d3b0c2b2a60fe60c6a/chart/templates/gitlab/values.yaml#L49) 

-**Packages connecting to a pre-existing database**

-2. Package chart accepts a secret name where all the DB connection info is defined. In these cases we make the secret in the BB chart..
+**Packages connecting to a pre-existing object storage**

- add conditional statement in `chart/templates/<package>/values.yaml` to add values for database secret, if database values exist. Otherwise the internal database is deployed.
+2. Package chart accepts a secret name where all the object storage connection info is defined. In these cases we make the secret in the BB chart.
+
+- add conditional statement in `chart/templates/<package>/values.yaml` to add values for object storage secret, if object storage values exist. Otherwise the minio cluster is used.
 ```yml
 {{- with .Values.addons.mattermost.objectStorage }}
 {{- if and .endpoint .accessKey .accessSecret .bucket }}
 @@ -101,21 +102,7 @@ minio:
 {{- end }}
 ```

-Example: [MatterMost](https://repo1.dso.mil/platform-one/big-bang/bigbang/-/blob/10d43bea9351b91dfc6f14d3b0c2b2a60fe60c6a/chart/templates/mattermost/mattermost/values.yaml#L63-77)
-
-???
-```yaml
-{{- if or .Values.addons.minio.enabled}}
-minio:
-  enabled: {{ .Values.<chartname>.minio.enabled }}
-    disableSSL: false
-    endpoint: {{  .Values.<chartname>.minio.endpoint }}
-    accessKey: {{   .Values.<chartname>.minio.accessKey }}
-    secretKey: {{   .Values.<chartname>.minio.secretKey }}
-    bucketName: {{   .Values.<chartname>.minio.bucketName }}
-{{ end }}
+Example: [GitLab secret-objectstore.yaml](https://repo1.dso.mil/platform-one/big-bang/bigbang/-/blob/master/chart/templates/gitlab/secret-objectstore.yaml)

-```
-???

 ## Validation