CLOUDP-346604: fixes for search snippets after 1.4.0 (#472)

# Summary

This PR fixes search snippets issued found after the release 1.4.0

## Proof of Work

Passing search snippets tests: [evg
link](https://spruce.mongodb.com/version/68d4f0827e318300077e3595/tasks?page=0&sorts=STATUS%3AASC%3BBASE_STATUS%3ADESC&variant=%5Eprivate_kind_code_snippets%24)

## Checklist

- [ ] Have you linked a jira ticket and/or is the ticket in the title?
- [ ] Have you checked whether your jira ticket required DOCSP changes?
- [ ] Have you added changelog file?
    - use `skip-changelog` label if not needed
- refer to [Changelog files and Release
Notes](https://github.com/mongodb/mongodb-kubernetes/blob/master/CONTRIBUTING.md#changelog-files-and-release-notes)
section in CONTRIBUTING.md for more details

Author: lsierant

docs/search/02-search-enterprise-deploy/code_snippets/02_0080_helm_login_to_prerelease_registry.sh

@@ -5,7 +5,7 @@ metadata:
   name: ${MDB_RESOURCE_NAME}
 spec:
   members: 3
-  version: ${MDB_VERSION}-ent
+  version: ${MDB_VERSION}
   type: ReplicaSet
   opsManager:
     configMapRef:
@@ -18,18 +18,17 @@ spec:
       modes:
       - SCRAM
   agent:
-    logLevel: DEBUG
-  statefulSet:
-    spec:
-      template:
-        spec:
-          containers:
-          - name: mongodb-enterprise-database
-            resources:
-              limits:
-                cpu: "2"
-                memory: 2Gi
-              requests:
-                cpu: "1"
-                memory: 1Gi
+    logLevel: INFO
+  podSpec:
+    podTemplate:
+      spec:
+        containers:
+        - name: mongodb-enterprise-database
+          resources:
+            limits:
+              cpu: "2"
+              memory: 2Gi
+            requests:
+              cpu: "1"
+              memory: 1Gi
 EOF

docs/search/02-search-enterprise-deploy/code_snippets/02_0305_create_mongodb_database_resource.sh

@@ -25,7 +25,7 @@ EOF
 # For MongoDB <8.2, the operator will be creating the searchCoordinator custom role automatically
 # From MongoDB 8.2, searchCoordinator role will be a built-in role.
 kubectl --context "${K8S_CTX}" --namespace "${MDB_NS}" \
-  create secret generic mdb-rs-search-sync-source-password \
+  create secret generic "${MDB_RESOURCE_NAME}-search-sync-source-password" \
   --from-literal=password="${MDB_SEARCH_SYNC_USER_PASSWORD}"
 kubectl apply --context "${K8S_CTX}" -n "${MDB_NS}" -f - <<EOF
 apiVersion: mongodb.com/v1
@@ -38,7 +38,7 @@ spec:
   mongodbResourceRef:
     name: ${MDB_RESOURCE_NAME}
   passwordSecretKeyRef:
-    name: mdb-rs-search-sync-source-password
+    name: ${MDB_RESOURCE_NAME}-search-sync-source-password
     key: password
   roles:
   - name: searchCoordinator

docs/search/02-search-enterprise-deploy/code_snippets/02_0315_create_mongodb_users.sh

@@ -1,2 +1,2 @@
 echo "Waiting for MongoDBSearch resource to reach Running phase..."
-kubectl --context "${K8S_CTX}" -n "${MDB_NS}" wait --for=jsonpath='{.status.phase}'=Running mdbs/mdb-rs --timeout=300s
+kubectl --context "${K8S_CTX}" -n "${MDB_NS}" wait --for=jsonpath='{.status.phase}'=Running "mdbs/${MDB_RESOURCE_NAME}" --timeout=300s

docs/search/02-search-enterprise-deploy/code_snippets/02_0325_wait_for_search_resource.sh

@@ -1,6 +1,6 @@
 echo; echo "MongoDB resource"
 kubectl --context "${K8S_CTX}" -n "${MDB_NS}" get "mdb/${MDB_RESOURCE_NAME}"
 echo; echo "MongoDBSearch resource"
-kubectl --context "${K8S_CTX}" -n "${MDB_NS}" get mdbs/mdb-rs
+kubectl --context "${K8S_CTX}" -n "${MDB_NS}" get "mdbs/${MDB_RESOURCE_NAME}"
 echo; echo "Pods running in cluster ${K8S_CTX}"
 kubectl --context "${K8S_CTX}" -n "${MDB_NS}" get pods

docs/search/02-search-enterprise-deploy/code_snippets/02_0335_show_running_pods.sh

@@ -14,13 +14,13 @@ export OPS_MANAGER_PROJECT_NAME="<arbitrary project name>"
 export OPS_MANAGER_API_URL="https://cloud-qa.mongodb.com"
 
 # The API key can be an Org Owner - the operator can create the project automatically then.
-# The API key can also be created in a particular project that was created manually with the Project Owner scope .
-export OPS_MANAGER_API_USER="abcdefg"
-export OPS_MANAGER_API_KEY="00000-abcd-efgh-1111-12345678"
-export OPS_MANAGER_ORG_ID="62a73abcdefgh12345678"
+# The API key can also be created in a particular project that was created manually with the Project Owner scope.
+export OPS_MANAGER_API_USER="<SET API USER>"
+export OPS_MANAGER_API_KEY="<SET API KEY>"
+export OPS_MANAGER_ORG_ID="<SET ORG ID>"
 
 # minimum required MongoDB version for running MongoDB Search is 8.0.10
-export MDB_VERSION="8.0.10"
+export MDB_VERSION="8.0.14-ent"
 
 # root admin user for convenience, not used here at all in this guide
 export MDB_ADMIN_USER_PASSWORD="admin-user-password-CHANGE-ME"

docs/search/02-search-enterprise-deploy/env_variables.sh

@@ -1 +1,7 @@
 export K8S_CTX="${CLUSTER_NAME}"
+
+export OPS_MANAGER_PROJECT_NAME="${NAMESPACE}-${MDB_RESOURCE_NAME}"
+export OPS_MANAGER_API_URL="${OM_BASE_URL}"
+export OPS_MANAGER_API_USER="${OM_USER}"
+export OPS_MANAGER_API_KEY="${OM_API_KEY}"
+export OPS_MANAGER_ORG_ID="${OM_ORGID}"