documentation update

docs/docs/bundles.md

@@ -84,7 +84,7 @@ The Policy /diag/config [API](api.md) (which is likely disabled in production en
 
 Original template automation for config map:
 
-   * [AWS Config map](https://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/blob/master/devops/aws/opa/templates/configmap.yaml)
+   * [M14-M17 AWS Config map helm charts](https://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/blob/master/devops/aws/opa/templates/configmap.yaml) - Please note in M18 AWS switched to [Terraform](https://community.opengroup.org/osdu/platform/deployment-and-operations/terraform-deployment-aws).
    * [Azure Config map](https://community.opengroup.org/osdu/platform/deployment-and-operations/helm-charts-azure/-/blob/master/osdu-azure/osdu-opa/templates/configmap-opa.yaml)
    * [GC](https://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/blob/master/devops/gc/deploy/templates/opa-configmap.yaml)
 
@@ -149,7 +149,13 @@ You will need add the following section:
 
     All values for [min_delay_seconds and max_delay_seconds](https://www.openpolicyagent.org/docs/latest/configuration/#bundles) are supported, but you might need to adjust [BUNDLE_PAUSE](testing.md#bundle_pause) if you are running automated integration tests in this new data partition.
 
-### Interactive update of config map (not recommended)
+### Applying Update
+
+!!! warning
+
+    You may not want to do this if your environment was created with cloudformation, helm or terraform. Use those methods to avoid conflicts.
+
+#### Interactive update of config map via kubectl (not recommended) 
 
 This can be tricky because of the spaces and newline \n in the data config section:
 ```
@@ -167,7 +173,7 @@ Interactive update example:
 kubectl -n osdu-services edit configmap opa-config
 ```
 
-### Apply Modifications from file
+#### Apply Modifications from file using kubectl
 
 ```
 kubectl apply -f configmap.yaml
@@ -178,4 +184,36 @@ kubectl apply -f configmap.yaml
 Example, your pod name and namespace may be different
 ```
 kubectl -n osdu-services logs  opa-agent-5ddf6fc476-lwp6p
+```
+
+### Helm
+
+If your environment is managed by helm.  Get RELEASE_NAME.
+```
+helm list -A
+```
+
+Values for helm
+```
+helm get values core -n osdu-services
+```
+
+If there isn't a section like this than you are currently only supporting the default partition `osdu`:
+```
+opa-agent:
+  partitions:
+  - osdu
+  - other partitions
+```
+
+Add the above to file opa-values.yaml
+
+Then update using helm (dry-run first):
+```
+helm upgrade core core/core --reuse-values --version 0.19.1 -f opa-values.yaml --dry-run
+```
+
+If no errors, for real:
+```
+helm upgrade core core/core --reuse-values --version 0.19.1 -f opa-values.yaml
 ```
\ No newline at end of file