Update Simapp configuration
Change-Id: I227dc7b41a74de23f9fa3c761b80abccc3de86a3
diff --git a/edge_deployment/connectivity_service_update.rst b/edge_deployment/connectivity_service_update.rst
index 2d3f048..d0b5429 100644
--- a/edge_deployment/connectivity_service_update.rst
+++ b/edge_deployment/connectivity_service_update.rst
@@ -39,7 +39,7 @@
Edit the simapp configuration and add the new IMSIs to sim management. The
file to edit depends on which Aether Connectivity Cluster serves the Enterprise
site. The appropriate file for standard Aether production is
-`aether-app-configs/apps/sim-app/overlays/prd-acc-gcp1/values.yaml`. Other
+`aether-app-configs/apps/sd-core-4g/overlays/prd-acc-gcp1/values.yaml`. Other
clusters will be located in similar directories.
The following example demonstrates adding IMSIs 123456789123460-123456789123465:
diff --git a/operations/subscriber.rst b/operations/subscriber.rst
index 333f9b6..e908760 100644
--- a/operations/subscriber.rst
+++ b/operations/subscriber.rst
@@ -22,7 +22,7 @@
Each UE is assigned a PLMN and a set of security keys. Depending on the deployment scenario, these
keys might be shared by several UEs, or they might be unique to each UE. The allocation of PLMNs and
keys is currently performed manually by the Aether Operations team. This subscriber-related
-detail is configured via the SIM Management application, ``Simapp``.
+detail is configured via the SIM Management application, ``simapp``.
``simapp.yaml`` needs to be adjusted to include the new UE IMSIs to the subscriber list. For example::
@@ -53,8 +53,12 @@
key: 8baf473f2f8fd09487cccbd7097c6862
sequenceNumber: 16f3b3f70fc2
-TODO: This file will probably be placed under GitOps control once the 5G ROC is deployed. Document
-the new location of the file.
+The simapp configurations for all deployments are stored in the ``aether-app-configs`` repository:
+
+* Production deployment: ``apps/sd-core-4g/overlays/prd-acc-gcp1/values.yaml``
+* Staging deployment: ``apps/sd-core-4g/overlays/stg-acc-aws/values.yaml``
+
+Fleet will automatically deploy changes to these files once they are merged.
.. _configure_device_group: