nmdc-runtime 1.5.0__tar.gz → 1.7.0__tar.gz

{nmdc_runtime-1.5.0 → nmdc_runtime-1.7.0}/.github/workflows/build-and-release-to-spin.yml

@@ -50,6 +50,7 @@ jobs:
         with:
           images: |
             microbiomedata/nmdc-runtime-${{ matrix.image }}
+            ghcr.io/microbiomedata/nmdc-runtime-${{ matrix.image }}
           flavor: |
             latest=false
           tags: |
@@ -63,6 +64,15 @@ jobs:
           username: ${{ secrets.DOCKERHUB_USERNAME }}
           password: ${{ secrets.DOCKERHUB_TOKEN }}
 
+      # Reference: https://docs.docker.com/build/ci/github-actions/push-multi-registries/
+      # Reference: https://docs.github.com/en/actions/learn-github-actions/contexts#github-context
+      - name: Login to GitHub Container Registry
+        uses: docker/login-action@v3
+        with:
+          registry: ghcr.io
+          username: ${{ github.actor }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
       - name: Build and push
         uses: docker/build-push-action@v5
         with:

{nmdc_runtime-1.5.0 → nmdc_runtime-1.7.0}/Makefile

@@ -3,14 +3,22 @@ init:
 	pip install -r requirements/dev.txt
 	pip install --editable .[dev]
 
+# Updates Python dependencies based upon the contents of the `requirements/main.in` and `requirements/dev.in` files.
+#
+# To omit the `--upgrade` option (included by default) when running `pip-compile`:
+# ```
+# $ make update-deps UPDATE_DEPS_MAIN_UPGRADE_OPT='' UPDATE_DEPS_DEV_UPGRADE_OPT=''
+# ```
+UPDATE_DEPS_MAIN_UPGRADE_OPT ?= --upgrade
+UPDATE_DEPS_DEV_UPGRADE_OPT ?= --upgrade
 update-deps:
     # --allow-unsafe pins packages considered unsafe: distribute, pip, setuptools.
 	pip install --upgrade pip-tools pip setuptools
-	pip-compile --upgrade --build-isolation \
+	pip-compile $(UPDATE_DEPS_MAIN_UPGRADE_OPT) --build-isolation \
 		--allow-unsafe --resolver=backtracking --strip-extras \
 		--output-file requirements/main.txt \
 		requirements/main.in
-	pip-compile --allow-unsafe --upgrade --build-isolation \
+	pip-compile --allow-unsafe $(UPDATE_DEPS_DEV_UPGRADE_OPT) --build-isolation \
 		--allow-unsafe --resolver=backtracking --strip-extras \
 		--output-file requirements/dev.txt \
 		requirements/dev.in

{nmdc_runtime-1.5.0 → nmdc_runtime-1.7.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: nmdc_runtime
-Version: 1.5.0
+Version: 1.7.0
 Summary: A runtime system for NMDC data management and orchestration
 Home-page: https://github.com/microbiomedata/nmdc-runtime
 Author: Donny Winston
@@ -77,18 +77,15 @@ The runtime features:
          - `schedules` trigger recurring pipeline runs based on time
          - `sensors` trigger pipeline runs based on external state
       - Each `pipeline` can declare dependencies on any runtime `resources` or additional
-         configuration. There are TerminusDB and MongoDB `resources` defined, as well as `preset`
+         configuration. There are MongoDB `resources` defined, as well as `preset`
          configuration definitions for both "dev" and "prod" `modes`. The `preset`s tell Dagster to
          look to a set of known environment variables to load resources configurations, depending on
          the `mode`.
-
-2. A [TerminusDB](https://terminusdb.com/) database supporting revision control of schema-validated
-data.
    
-3. A MongoDB database supporting write-once, high-throughput internal
+2. A MongoDB database supporting write-once, high-throughput internal
 data storage by the nmdc-runtime FastAPI instance.
    
-4. A [FastAPI](https://fastapi.tiangolo.com/) service to interface with the orchestrator and
+3. A [FastAPI](https://fastapi.tiangolo.com/) service to interface with the orchestrator and
 database, as a hub for data management and workflow automation.
 
 ## Local Development

{nmdc_runtime-1.5.0 → nmdc_runtime-1.7.0}/README.md

@@ -63,18 +63,15 @@ The runtime features:
          - `schedules` trigger recurring pipeline runs based on time
          - `sensors` trigger pipeline runs based on external state
       - Each `pipeline` can declare dependencies on any runtime `resources` or additional
-         configuration. There are TerminusDB and MongoDB `resources` defined, as well as `preset`
+         configuration. There are MongoDB `resources` defined, as well as `preset`
          configuration definitions for both "dev" and "prod" `modes`. The `preset`s tell Dagster to
          look to a set of known environment variables to load resources configurations, depending on
          the `mode`.
-
-2. A [TerminusDB](https://terminusdb.com/) database supporting revision control of schema-validated
-data.
    
-3. A MongoDB database supporting write-once, high-throughput internal
+2. A MongoDB database supporting write-once, high-throughput internal
 data storage by the nmdc-runtime FastAPI instance.
    
-4. A [FastAPI](https://fastapi.tiangolo.com/) service to interface with the orchestrator and
+3. A [FastAPI](https://fastapi.tiangolo.com/) service to interface with the orchestrator and
 database, as a hub for data management and workflow automation.
 
 ## Local Development