Merge branch 'develop' into promotions/2026-01-27-anvilprod

Author: dsotirho-ucsc

OPERATOR.rst

@@ -290,11 +290,11 @@ Updating the AMI for GitLab instances
 
 As part of the upgrades isssue, operators must check for updates to the AMI for
 the root volume of the EC2 instance running GitLab. We use a hardened — to the
-requirements of the CIS Amazon Linux 2 benchmark — variant of Amazon's Linux 2
-AMI. The license to use the AMI for an EC2 instance is sold by CIS as a
-subscription on the AWS Marketplace:
+requirements of the CIS Hardened Image Level 1 on Amazon Linux 2023. The license
+to use the AMI for an EC2 instance is sold by CIS as a subscription on the AWS
+Marketplace:
 
-https://aws.amazon.com/marketplace/pp/prodview-wv574yqgjv6jg
+https://aws.amazon.com/marketplace/pp/prodview-fqqp6ebucarnm
 
 The license costs $0.024 per instance/hour. Every AWS account must subscribe
 separately.
@@ -313,7 +313,7 @@ component, say, ``_select dev.gitlab`` and run
 
     aws ec2 describe-images \
             --owners aws-marketplace \
-            --filters="Name=name,Values=*abcfcbaf-134e-4639-a7b4-fd285b9fcf0a*" \
+            --filters="Name=name,Values=*prod-fvm47vekg24oc*" \
         | jq -r '.Images[] | .CreationDate+"\t"+.ImageId+"\t"+.Name' \
         | sort \
         | tail -1
@@ -698,7 +698,7 @@ you can simply jump to `Launching ZAP`_.
    temporarily blocked by the system, you will need to configure the maximum
    rate of requests that ZAP will send out. From the app menu bar, select
    *Tools*, then *Options*, then *Network*, then *Rate Limit*. Add and enable a
-   three request per second rule for the match string ``anvilprod.org``, and
+   three request per second rule for the match string ``anvilproject.org``, and
    another rule for the match string ``humancellatlas.org``.
 
 #. With the *Options* window open, select *Check for Updates* from the list of

README.md

@@ -875,7 +875,10 @@ but they will be empty.
    `deployments/.active/.terraform.{$AWS_PROFILE}/terraform.tfstate`.
 
 
-# 4. Running indexer or service locally
+# 4. Running system components locally
+
+
+## 4.1 Running indexer or service locally
 
 While this method *does* run the service or indexer locally on your machine, it
 still requires that the cloud resources used by them are already deployed.
@@ -898,6 +901,27 @@ PyCharm recently added a feature that allows you to attach a debugger: From the
 main menu choose *Run*, *Attach to local process* and select the `chalice`
 process.
 
+## 4.2 Running the Data Browser locally
+
+Follow the steps in the [Data Browser's README] to install the prerequisites
+and launch a local version of the Data Browser's server.
+
+[Data Browser's README]: https://github.com/DataBiosphere/data-browser/blob/main/README.md
+
+The argument you specify in the launch command controls which deployment of Azul
+the server will connect to (e.g. `dev:hca-dcp` for the HCA `dev` deployment).
+To connect to another Azul deployment, see the list of site configs in the
+`/site-config` folder. To connect to a personal deployment of Azul, temporarily
+modify a related site config (e.g. `/site-config/hca-dcp/dev/config.ts` for an
+HCA-based personal deployment), set the `CATALOG` and `DATA_URL` properties to
+values matching your personal deployment, and then launch the Data Browser's
+server with the modified config specified.
+
+Note that when run locally, the Data Browser will make duplicate requests to
+Azul on every page load. This is due to React being run in dev mode with
+StrictMode enabled. To disable this behavior, modify `/next.config.mjs` and set
+the `reactStrictMode` property to false.
+
 
 # 5. Troubleshooting
 

UPGRADING.rst

@@ -20,6 +20,23 @@ reverted. This is all fairly informal and loosely defined. Hopefully we won't
 have too many entries in this file.
 
 
+#7128 Add support for HCA atlas (partial)
+=========================================
+
+In your personal HCA deployments, add the following snapshots to the ``dcp3``
+catalog:
+
+- ``8c4e43fb…``
+- ``8f1f653d…``
+- ``aca93e28…``
+- ``c0518445…``
+- ``c4e11369…``
+- ``edc54c5d…``
+
+As always, use the sandbox deployment's ``environment.py`` as a model when
+upgrading personal deployments.
+
+
 #7617 Index one snapshot from upcoming lm10 release in `dev`
 ============================================================