Skip to content

[#2723] Extracted the container image deployment from 'export-db' into a dedicated script.#2727

Merged
AlexSkrypnyk merged 1 commit into
mainfrom
feature/2723-export-db-deploy
Jun 26, 2026
Merged

[#2723] Extracted the container image deployment from 'export-db' into a dedicated script.#2727
AlexSkrypnyk merged 1 commit into
mainfrom
feature/2723-export-db-deploy

Conversation

@AlexSkrypnyk

@AlexSkrypnyk AlexSkrypnyk commented Jun 25, 2026

Copy link
Copy Markdown
Member

Closes #2723

Checklist before requesting a review

  • Subject includes ticket number as [#123] Verb in past tense.
  • Ticket number #2723 added to description
  • Added context in Changed section
  • Self-reviewed code and commented in commented complex areas.
  • Added tests for fix/feature.
  • Relevant tests run and passed locally.

Changed

  1. Added .vortex/tooling/src/deploy-db-image: a dedicated, independently-callable script that deploys an exported database container image to the container registry. It is gated by VORTEX_EXPORT_DB_CONTAINER_REGISTRY_DEPLOY_PROCEED, resolves VORTEX_EXPORT_DB_IMAGE (falling back to VORTEX_DB_IMAGE), builds VORTEX_DEPLOY_CONTAINER_REGISTRY_MAP=database=<image>, and delegates to deploy-container-registry.
  2. Reduced .vortex/tooling/src/export-db to a pure exporter: removed the inline container-registry deployment and the # @todo Move deployment into a separate script. comment. export-db now only exports a database (file or image) and no longer knows anything about deployment.
  3. Wired the deployment as a separate Deploy DB image step in the CircleCI database job (.circleci/config.yml), after Export DB after fetch. It is a no-op unless the project uses database-in-image storage (VORTEX_DB_IMAGE) and a fresh database was fetched this run (the /tmp/fetch-db-fresh semaphore); deploy-db-image then additionally requires VORTEX_EXPORT_DB_CONTAINER_REGISTRY_DEPLOY_PROCEED=1. This preserves the prior behaviour (only the CircleCI nightly job deploys) while taking deployment out of export-db.
  4. Renamed the fetch semaphore file from /tmp/fetch-db-success to /tmp/fetch-db-fresh (in both .circleci/config.yml and .github/workflows/build-test-deploy.yml), since fetch-db writes it only on a genuine fresh fetch, not on a cache hit - the name now states what the file means.
  5. Regenerated .circleci/vortex-test-common.yml (via php .vortex/tests/generate-vortex-dev-circleci) and the installer fixtures (via ahoy update-snapshots).
  6. Added .vortex/tooling/tests/unit/deploy-db-image.bats (5 tests: skips when deployment is not requested; deploys with the correct registry map; resolves the image from the VORTEX_DB_IMAGE fallback; fails when no image name is set; fails when the registry deployment fails). Updated .vortex/tooling/tests/unit/export-db.bats to assert export-db only exports, removing the deploy assertions since deployment has left export-db.

Screenshots

N/A

Before / After

BEFORE - deployment is fused into the exporter
────────────────────────────────────────────────────────────────
CI "Export DB after fetch" step  (gated: fresh fetch)
  └── export-db db.sql
        └── export-db-image                       image built
              └── if PROCEED=1                     ← deploy lives
                    deploy-container-registry         inside export

AFTER - export and deploy are separate steps, each gated
────────────────────────────────────────────────────────────────
CI "Export DB after fetch" step  (gated: fresh fetch)
  └── export-db db.sql
        └── export-db-image                       image built

CI "Deploy DB image" step
  ├── gate: VORTEX_DB_IMAGE set              (database-in-image)
  ├── gate: /tmp/fetch-db-fresh present      (fresh DB this run)
  └── deploy-db-image
        └── gate: PROCEED=1                   (operator opt-in)
              VORTEX_DEPLOY_CONTAINER_REGISTRY_MAP=database=<image>
                deploy-container-registry

@github-project-automation github-project-automation Bot moved this to BACKLOG in Vortex 1.x Jun 25, 2026
@AlexSkrypnyk AlexSkrypnyk added this to the 1.40.0 milestone Jun 25, 2026
@AlexSkrypnyk AlexSkrypnyk added the A4 Board worker 4 label Jun 25, 2026
@coderabbitai

coderabbitai Bot commented Jun 25, 2026

Copy link
Copy Markdown

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Walkthrough

A new deploy-db-image script was added, export-db now routes image exports through export-db-image, and CircleCI adds a gated DB-image deployment step after export.

Changes

DB image deployment extraction

Layer / File(s) Summary
Deployment script and tests
.vortex/tooling/src/deploy-db-image, .vortex/tooling/tests/unit/deploy-db-image.bats
The new script loads env files, resolves the DB image name, checks the proceed flag, builds VORTEX_DEPLOY_CONTAINER_REGISTRY_MAP, and calls deploy-container-registry; the unit tests cover skip, success, fallback, missing image, and failure propagation cases.
Host export routing
.vortex/tooling/src/export-db, .vortex/tooling/tests/unit/export-db.bats
The host export-db branch now invokes export-db-image when VORTEX_EXPORT_DB_IMAGE is set, and the updated test only checks the export-image path.
CircleCI deploy step
.circleci/vortex-test-common.yml, .circleci/config.yml
The database job updates its fetch semaphore name and adds a deploy step that runs deploy-db-image only when /tmp/fetch-db-fresh exists and VORTEX_DB_IMAGE is non-empty.

Sequence Diagram(s)

CircleCI deployment flow

sequenceDiagram
  participant CircleCI database job
  participant deploy-db-image
  participant deploy-container-registry
  CircleCI database job->>deploy-db-image: run when semaphore exists and VORTEX_DB_IMAGE is set
  deploy-db-image->>deploy-container-registry: deploy database=<image>
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

  • drevops/vortex#2724: Changes the export-db host-side routing around VORTEX_EXPORT_DB_IMAGE, which this PR continues by extracting the deployment step.

Suggested labels

Needs review

Poem

🐰 I hopped through export, bright and keen,
Then danced where deploy scripts now convene.
The registry twinkled, the DB image spun,
And the little CI moon said, “Job well done!”

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: extracting database image deployment into a dedicated script.
Linked Issues check ✅ Passed The PR removes deployment from export-db, adds a standalone deploy-db-image script, preserves the proceed guard, removes the todo, and adds tests.
Out of Scope Changes check ✅ Passed The CircleCI wiring and test updates support the stated extraction and deployment workflow, with no clear unrelated changes.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feature/2723-export-db-deploy

Comment @coderabbitai help to get the list of available commands.

@AlexSkrypnyk

This comment has been minimized.

@github-actions

This comment has been minimized.

@AlexSkrypnyk

This comment has been minimized.

1 similar comment
@AlexSkrypnyk

This comment has been minimized.

@github-actions

github-actions Bot commented Jun 25, 2026

Copy link
Copy Markdown

📖 Documentation preview for this pull request has been deployed to Netlify:

https://6a3dd9465b6b9c25428af951--vortex-docs.netlify.app

This preview is rebuilt on every commit and is not the production documentation site.

@codecov

codecov Bot commented Jun 25, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.22%. Comparing base (c018252) to head (44e23fc).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2727      +/-   ##
==========================================
- Coverage   86.67%   86.22%   -0.45%     
==========================================
  Files          96       89       -7     
  Lines        4719     4560     -159     
  Branches       47        3      -44     
==========================================
- Hits         4090     3932     -158     
+ Misses        629      628       -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@AlexSkrypnyk AlexSkrypnyk force-pushed the feature/2723-export-db-deploy branch from e604d68 to 245c6b6 Compare June 25, 2026 22:59
@AlexSkrypnyk AlexSkrypnyk changed the title [#2723] Extracted container image deployment from 'export-db' into a dedicated 'deploy-db-image' script. [#2723] Extracted the container image deployment from 'export-db' into a dedicated script. Jun 25, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
.github/workflows/build-test-deploy.yml (1)

302-323: 🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Add the post-export DB image deploy step to the GitHub workflow.

After Line 304, this job goes straight to Save DB cache, while the CircleCI jobs in this PR now invoke deploy-db-image after a fresh download/export. As written, GitHub Actions never publishes the freshly exported DB image here even when deployment is requested, so the new flow is only wired on one CI provider.

Suggested change
       - name: Export DB
         run: |
           if [ ! -f /tmp/download-db-fresh ]; then echo "==> No freshly downloaded database. DB export will not proceed."; exit 0; fi
           ./vendor/drevops/vortex-tooling/src/login-container-registry
           docker compose up --detach && sleep 15
           docker compose exec cli mkdir -p .data && docker compose cp -L .data/db.sql cli:/app/.data/db.sql
           docker compose exec cli bash -c "VORTEX_PROVISION_POST_OPERATIONS_SKIP=1 ./vendor/drevops/vortex-tooling/src/provision"
           ./vendor/drevops/vortex-tooling/src/export-db db.sql
           docker compose cp -L cli:/app/.data/db.sql .data/db.sql
         timeout-minutes: 30

+      - name: Deploy DB image
+        run: |
+          if [ ! -f /tmp/download-db-fresh ]; then echo "==> No freshly downloaded database. DB image deployment will not proceed."; exit 0; fi
+          if [ -z "${VORTEX_DB_IMAGE:-}" ]; then echo "==> Database-in-image storage is not used. DB image deployment will not proceed."; exit 0; fi
+          ./vendor/drevops/vortex-tooling/src/deploy-db-image
+        timeout-minutes: 30
+
       # Save cache per default branch and the timestamp.
       # The cache will not be saved if it already exists.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/build-test-deploy.yml around lines 302 - 323, The GitHub
Actions workflow is missing the post-export DB image deployment step, so the
fresh export path in this job stops at Export DB and never publishes the image
when deployment is requested. Update the workflow around the Export DB and Save
DB cache steps to invoke the same deploy-db-image flow that CircleCI uses after
a fresh database download/export, making sure the new step runs before caching
and is wired into the existing DB export logic.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.vortex/tooling/tests/unit/deploy-db-image.bats:
- Around line 21-22: The deploy-db-image Bats tests are relying on unset
variables, which lets values from .env.local leak into the skip/fallback/failure
cases and make them nondeterministic. Update the affected setup blocks in
deploy-db-image.bats to use explicit exported empty or 0 values instead of unset
so the test-controlled environment overrides any repo-local defaults. Apply this
consistently in the cases around the existing
VORTEX_EXPORT_DB_CONTAINER_REGISTRY_DEPLOY_PROCEED and VORTEX_EXPORT_DB_IMAGE
assignments.

---

Outside diff comments:
In @.github/workflows/build-test-deploy.yml:
- Around line 302-323: The GitHub Actions workflow is missing the post-export DB
image deployment step, so the fresh export path in this job stops at Export DB
and never publishes the image when deployment is requested. Update the workflow
around the Export DB and Save DB cache steps to invoke the same deploy-db-image
flow that CircleCI uses after a fresh database download/export, making sure the
new step runs before caching and is wired into the existing DB export logic.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 96abca36-9f00-4f88-b788-2eb877c96bef

📥 Commits

Reviewing files that changed from the base of the PR and between e604d68 and 245c6b6.

⛔ Files ignored due to path filters (33)
  • .vortex/installer/tests/Fixtures/handler_process/_baseline/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/ciprovider_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/code_coverage_provider_codecov_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/db_download_source_acquia/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/deploy_types_all_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/deploy_types_none_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/deps_updates_provider_ci_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/hosting_acquia/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/hosting_project_name___acquia/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_disabled_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_download_source_acquia/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_download_source_container_registry/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_download_source_ftp/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_download_source_lagoon/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_download_source_s3/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_download_source_url/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_enabled/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_enabled_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_enabled_lagoon/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/provision_profile/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/timezone_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_be_lint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_be_tests_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_fe_lint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_fe_lint_no_theme_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_behat_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_eslint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_jest_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_phpcs_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_phpstan_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_phpunit_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_rector_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_stylelint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
📒 Files selected for processing (7)
  • .circleci/config.yml
  • .circleci/vortex-test-common.yml
  • .github/workflows/build-test-deploy.yml
  • .vortex/tooling/src/deploy-db-image
  • .vortex/tooling/src/export-db
  • .vortex/tooling/tests/unit/deploy-db-image.bats
  • .vortex/tooling/tests/unit/export-db.bats
💤 Files with no reviewable changes (2)
  • .vortex/tooling/src/export-db
  • .vortex/tooling/tests/unit/export-db.bats

Comment thread .vortex/tooling/tests/unit/deploy-db-image.bats
@github-actions

This comment has been minimized.

@AlexSkrypnyk

This comment has been minimized.

2 similar comments
@AlexSkrypnyk

This comment has been minimized.

@AlexSkrypnyk

This comment has been minimized.

@github-actions github-actions Bot added the CONFLICT Pull request has a conflict that needs to be resolved before it can be merged label Jun 25, 2026
@AlexSkrypnyk AlexSkrypnyk force-pushed the feature/2723-export-db-deploy branch from 245c6b6 to ad62efd Compare June 25, 2026 23:20

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
.github/workflows/build-test-deploy.yml (1)

302-311: 🗄️ Data Integrity & Integration | 🟠 Major

Add the Deploy DB image step after Export DB
This workflow exports the DB but never runs deploy-db-image, unlike the CircleCI configs. If GitHub Actions should also publish DB images when VORTEX_EXPORT_DB_CONTAINER_REGISTRY_DEPLOY_PROCEED=1, add the same gated step here.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/build-test-deploy.yml around lines 302 - 311, The
workflow’s Export DB sequence is missing the gated DB image publish step, so add
a new step after Export DB that runs deploy-db-image only when
VORTEX_EXPORT_DB_CONTAINER_REGISTRY_DEPLOY_PROCEED is set to 1, matching the
existing CircleCI behavior. Place it in the same job near the existing Export DB
commands and reuse the same gating pattern so the DB export flow and image
deployment stay aligned.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In @.github/workflows/build-test-deploy.yml:
- Around line 302-311: The workflow’s Export DB sequence is missing the gated DB
image publish step, so add a new step after Export DB that runs deploy-db-image
only when VORTEX_EXPORT_DB_CONTAINER_REGISTRY_DEPLOY_PROCEED is set to 1,
matching the existing CircleCI behavior. Place it in the same job near the
existing Export DB commands and reuse the same gating pattern so the DB export
flow and image deployment stay aligned.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 1075211a-ff3a-4b93-a4be-76cdc1f983c6

📥 Commits

Reviewing files that changed from the base of the PR and between 245c6b6 and ad62efd.

⛔ Files ignored due to path filters (33)
  • .vortex/installer/tests/Fixtures/handler_process/_baseline/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/ciprovider_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/code_coverage_provider_codecov_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/db_download_source_acquia/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/deploy_types_all_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/deploy_types_none_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/deps_updates_provider_ci_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/hosting_acquia/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/hosting_project_name___acquia/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_disabled_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_download_source_acquia/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_download_source_container_registry/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_download_source_ftp/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_download_source_lagoon/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_download_source_s3/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_download_source_url/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_enabled/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_enabled_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_enabled_lagoon/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/provision_profile/.github/workflows/build-test-deploy.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/timezone_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_be_lint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_be_tests_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_fe_lint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_fe_lint_no_theme_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_behat_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_eslint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_jest_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_phpcs_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_phpstan_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_phpunit_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_rector_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_stylelint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
📒 Files selected for processing (7)
  • .circleci/config.yml
  • .circleci/vortex-test-common.yml
  • .github/workflows/build-test-deploy.yml
  • .vortex/tooling/src/deploy-db-image
  • .vortex/tooling/src/export-db
  • .vortex/tooling/tests/unit/deploy-db-image.bats
  • .vortex/tooling/tests/unit/export-db.bats
💤 Files with no reviewable changes (2)
  • .vortex/tooling/src/export-db
  • .vortex/tooling/tests/unit/export-db.bats

@AlexSkrypnyk

This comment has been minimized.

2 similar comments
@AlexSkrypnyk

This comment has been minimized.

@AlexSkrypnyk

This comment has been minimized.

@AlexSkrypnyk AlexSkrypnyk added the Needs review Pull request needs a review from assigned developers label Jun 25, 2026
@github-actions github-actions Bot removed the Needs review Pull request needs a review from assigned developers label Jun 26, 2026
@AlexSkrypnyk AlexSkrypnyk force-pushed the feature/2723-export-db-deploy branch from ad62efd to 4ff1e3e Compare June 26, 2026 00:24
@github-actions github-actions Bot removed the CONFLICT Pull request has a conflict that needs to be resolved before it can be merged label Jun 26, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.vortex/tooling/src/export-db:
- Around line 7-8: The router header in the export-db entry script has diverged
from the shared wording used by the other Vortex entry routers, which makes the
trio inconsistent. Update the top-of-file comment in export-db so it matches the
standard host-router header used by import-db and download-db, keeping the
shared “IMPORTANT! This script runs outside the container on the host system.”
wording unless you are updating all three routers together.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: e54e01cd-c215-4900-986e-9383a118f11d

📥 Commits

Reviewing files that changed from the base of the PR and between ad62efd and 4ff1e3e.

⛔ Files ignored due to path filters (20)
  • .vortex/installer/tests/Fixtures/handler_process/ciprovider_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/code_coverage_provider_codecov_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/deploy_types_all_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/deploy_types_none_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/deps_updates_provider_ci_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_disabled_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_enabled_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/timezone_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_be_lint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_be_tests_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_fe_lint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_fe_lint_no_theme_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_behat_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_eslint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_jest_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_phpcs_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_phpstan_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_phpunit_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_rector_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_stylelint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
📒 Files selected for processing (6)
  • .circleci/config.yml
  • .circleci/vortex-test-common.yml
  • .vortex/tooling/src/deploy-db-image
  • .vortex/tooling/src/export-db
  • .vortex/tooling/tests/unit/deploy-db-image.bats
  • .vortex/tooling/tests/unit/export-db.bats
💤 Files with no reviewable changes (1)
  • .vortex/tooling/tests/unit/export-db.bats

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Inline review comments failed to post. This is likely due to GitHub's internal server error or limits when posting large numbers of comments. If you are seeing this consistently it is likely a permissions issue. Please check "Moderation" -> "Code review limits" under your organization settings.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.vortex/tooling/src/export-db:
- Around line 7-8: The router header in the export-db entry script has diverged
from the shared wording used by the other Vortex entry routers, which makes the
trio inconsistent. Update the top-of-file comment in export-db so it matches the
standard host-router header used by import-db and download-db, keeping the
shared “IMPORTANT! This script runs outside the container on the host system.”
wording unless you are updating all three routers together.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: e54e01cd-c215-4900-986e-9383a118f11d

📥 Commits

Reviewing files that changed from the base of the PR and between ad62efd and 4ff1e3e.

⛔ Files ignored due to path filters (20)
  • .vortex/installer/tests/Fixtures/handler_process/ciprovider_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/code_coverage_provider_codecov_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/deploy_types_all_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/deploy_types_none_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/deps_updates_provider_ci_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_disabled_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_enabled_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/timezone_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_be_lint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_be_tests_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_fe_lint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_fe_lint_no_theme_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_behat_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_eslint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_jest_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_phpcs_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_phpstan_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_phpunit_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_rector_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_stylelint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
📒 Files selected for processing (6)
  • .circleci/config.yml
  • .circleci/vortex-test-common.yml
  • .vortex/tooling/src/deploy-db-image
  • .vortex/tooling/src/export-db
  • .vortex/tooling/tests/unit/deploy-db-image.bats
  • .vortex/tooling/tests/unit/export-db.bats
💤 Files with no reviewable changes (1)
  • .vortex/tooling/tests/unit/export-db.bats
🛑 Comments failed to post (1)
.vortex/tooling/src/export-db (1)

7-8: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Keep the standard host-router header here.

Lines 7-8 now diverge from the shared wording used by the other Vortex entry routers. This file is intentionally documented as a host-side router, so changing only this header makes the trio inconsistent. Based on learnings, import-db, export-db, and download-db should keep the shared IMPORTANT! This script runs outside the container on the host system. header unless all three are updated together.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.vortex/tooling/src/export-db around lines 7 - 8, The router header in the
export-db entry script has diverged from the shared wording used by the other
Vortex entry routers, which makes the trio inconsistent. Update the top-of-file
comment in export-db so it matches the standard host-router header used by
import-db and download-db, keeping the shared “IMPORTANT! This script runs
outside the container on the host system.” wording unless you are updating all
three routers together.

Source: Learnings

@github-actions

This comment has been minimized.

@AlexSkrypnyk

This comment has been minimized.

2 similar comments
@AlexSkrypnyk

This comment has been minimized.

@AlexSkrypnyk

This comment has been minimized.

@AlexSkrypnyk AlexSkrypnyk force-pushed the feature/2723-export-db-deploy branch from 4ff1e3e to 2f5485d Compare June 26, 2026 01:13

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.circleci/config.yml:
- Line 281: The semaphore guard in the CircleCI config is malformed because the
test expression is missing a space before the closing bracket, causing a shell
syntax error and breaking the intended short-circuit check. Update both
occurrences of the `/tmp/fetch-db-fresh` guard to use a valid test command so
the `&&` chain only continues when the file is missing, and keep the surrounding
DB export gating logic intact.
- Line 299: The `Deploy DB image` gate has the same missing-space bug in the
shell test expression, so fix the `[ ! -f /tmp/fetch-db-fresh]` check by
correcting the spacing before the closing bracket in the existing one-liner.
Update the conditional in the DB image deployment step so it matches the valid
`test` syntax used elsewhere in the config and the exit guard works as intended.
- Line 262: The Fetch DB CircleCI command is broken because the environment
assignment and script path were merged into a single token, so the command never
runs. Update the command in the CircleCI config so the VORTEX_FETCH_DB_SEMAPHORE
assignment is separated from the fetch-db script invocation, using the existing
fetch-db command reference under the command block.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: d4624d08-7265-4907-90f9-4b95dc43c3bf

📥 Commits

Reviewing files that changed from the base of the PR and between 4ff1e3e and 2f5485d.

⛔ Files ignored due to path filters (20)
  • .vortex/installer/tests/Fixtures/handler_process/ciprovider_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/code_coverage_provider_codecov_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/deploy_types_all_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/deploy_types_none_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/deps_updates_provider_ci_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_disabled_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/migration_enabled_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/timezone_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_be_lint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_be_tests_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_fe_lint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_groups_no_fe_lint_no_theme_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_behat_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_eslint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_jest_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_phpcs_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_phpstan_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_phpunit_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_rector_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
  • .vortex/installer/tests/Fixtures/handler_process/tools_no_stylelint_circleci/.circleci/config.yml is excluded by !.vortex/installer/tests/Fixtures/**
📒 Files selected for processing (6)
  • .circleci/config.yml
  • .circleci/vortex-test-common.yml
  • .vortex/tooling/src/deploy-db-image
  • .vortex/tooling/src/export-db
  • .vortex/tooling/tests/unit/deploy-db-image.bats
  • .vortex/tooling/tests/unit/export-db.bats
💤 Files with no reviewable changes (2)
  • .vortex/tooling/tests/unit/export-db.bats
  • .vortex/tooling/src/export-db

Comment thread .circleci/config.yml Outdated
Comment thread .circleci/config.yml Outdated
Comment thread .circleci/config.yml Outdated
@AlexSkrypnyk AlexSkrypnyk moved this from BACKLOG to In progress in Vortex 1.x Jun 26, 2026
@github-actions

This comment has been minimized.

@AlexSkrypnyk

This comment has been minimized.

2 similar comments
@AlexSkrypnyk

This comment has been minimized.

@AlexSkrypnyk

This comment has been minimized.

@AlexSkrypnyk AlexSkrypnyk force-pushed the feature/2723-export-db-deploy branch from 2f5485d to 44e23fc Compare June 26, 2026 01:31
@github-actions

Copy link
Copy Markdown

Code coverage (threshold: 90%)

  Classes: 100.00% (1/1)
  Methods: 100.00% (2/2)
  Lines:   98.55% (204/207)
Per-class coverage
Drupal\ys_demo\Plugin\Block\CounterBlock
  Methods: 100.00% ( 2/ 2)   Lines: 100.00% ( 10/ 10)

@AlexSkrypnyk

This comment has been minimized.

2 similar comments
@AlexSkrypnyk

This comment has been minimized.

@AlexSkrypnyk

Copy link
Copy Markdown
Member Author

Code coverage (threshold: 90%)

  Classes: 100.00% (1/1)
  Methods: 100.00% (2/2)
  Lines:   98.55% (204/207)
Per-class coverage
Drupal\ys_demo\Plugin\Block\CounterBlock
  Methods: 100.00% ( 2/ 2)   Lines: 100.00% ( 10/ 10)

@AlexSkrypnyk AlexSkrypnyk merged commit 364f8de into main Jun 26, 2026
34 checks passed
@AlexSkrypnyk AlexSkrypnyk deleted the feature/2723-export-db-deploy branch June 26, 2026 02:22
@github-project-automation github-project-automation Bot moved this from In progress to Release queue in Vortex 1.x Jun 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A4 Board worker 4

Projects

Status: Release queue

Development

Successfully merging this pull request may close these issues.

Extract the container image deployment from 'export-db' into a dedicated script

1 participant