Fixed incorrectly prefixed environment variables.#2265
Conversation
WalkthroughThis PR consistently renames environment variables across the repo: Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
scripts/vortex/download-db-lagoon.sh (1)
87-96:⚠️ Potential issue | 🔴 CriticalThe
VORTEX_SSH_PREFIXmust be changed to match the variable naming convention.The script sets
VORTEX_SSH_PREFIX="DB_DOWNLOAD", butsetup-ssh.shconstructs variable names asVORTEX_${VORTEX_SSH_PREFIX}_SSH_*(lines 46, 54). This causes it to look forVORTEX_DB_DOWNLOAD_SSH_FINGERPRINTandVORTEX_DB_DOWNLOAD_SSH_FILE, which don't exist. The actual variables defined areVORTEX_DOWNLOAD_DB_SSH_FINGERPRINTandVORTEX_DOWNLOAD_DB_SSH_FILE(lines 47, 50), so the prefix must beDOWNLOAD_DB.Without this fix, the SSH fingerprint and file settings will be ignored, and the default
~/.ssh/id_rsawill be used instead.Required fix
-export VORTEX_SSH_PREFIX="DB_DOWNLOAD" && . ./scripts/vortex/setup-ssh.sh +export VORTEX_SSH_PREFIX="DOWNLOAD_DB" && . ./scripts/vortex/setup-ssh.sh
🤖 Fix all issues with AI agents
In @.env:
- Line 189: The .env file contains a duplicate key VORTEX_DOWNLOAD_DB_URL
(placeholder at top and demo URL later); to clarify intent either comment out or
remove the placeholder entry (the one currently empty) or add an inline comment
next to that placeholder explicitly stating it is intentionally overridden by
the DEMO section (reference the VORTEX_DOWNLOAD_DB_URL key) so readers and
parsers won’t be confused about which value is used.
In `@scripts/vortex/download-db.sh`:
- Line 18: Update the default for the VORTEX_DOWNLOAD_DB_SOURCE environment
variable from "curl" to "url" by changing the assignment of
VORTEX_DOWNLOAD_DB_SOURCE (the line setting
VORTEX_DOWNLOAD_DB_SOURCE="${VORTEX_DOWNLOAD_DB_SOURCE:-curl}") so it defaults
to "url"; this aligns with the supported source handlers (ftp, url, acquia,
lagoon, container_registry, s3) and the unit tests in download-db.bats so the
download path executes correctly when no source is provided.
In `@scripts/vortex/export-db-image.sh`:
- Around line 14-27: You modified the core vortex export script variables
(VORTEX_EXPORT_DB_IMAGE_ARCHIVE_FILE, VORTEX_EXPORT_DB_IMAGE,
VORTEX_EXPORT_DB_CONTAINER_REGISTRY, VORTEX_EXPORT_DB_SERVICE_NAME,
VORTEX_EXPORT_DB_IMAGE_DIR); per repo guidelines these changes must not live in
the core scripts directory—move the edited logic into a new script under the
custom scripts area (preserve the same variable names and behavior) and revert
the edits to the original core script, or if this is an intentional template
change, add a clear justification in the PR description and request owner
approval.
| # | ||
| # HTTP Basic Authentication credentials should be embedded into the value. | ||
| VORTEX_DB_DOWNLOAD_URL= | ||
| VORTEX_DOWNLOAD_DB_URL= |
There was a problem hiding this comment.
Duplicate key VORTEX_DOWNLOAD_DB_URL detected.
The variable VORTEX_DOWNLOAD_DB_URL is defined twice: once as an empty placeholder (line 189) and again in the DEMO section (line 303) with a demo URL. While this appears intentional for demonstration purposes, duplicate keys can cause confusion. The behavior depends on the parsing method—typically the last value wins.
Consider adding a comment near line 189 indicating that this value is overridden in the DEMO section, or commenting out the placeholder definition to make the intentional override clearer.
Also applies to: 303-303
🤖 Prompt for AI Agents
In @.env at line 189, The .env file contains a duplicate key
VORTEX_DOWNLOAD_DB_URL (placeholder at top and demo URL later); to clarify
intent either comment out or remove the placeholder entry (the one currently
empty) or add an inline comment next to that placeholder explicitly stating it
is intentionally overridden by the DEMO section (reference the
VORTEX_DOWNLOAD_DB_URL key) so readers and parsers won’t be confused about which
value is used.
| # Container image archive file name. | ||
| VORTEX_DB_EXPORT_IMAGE_ARCHIVE_FILE="${VORTEX_DB_EXPORT_IMAGE_ARCHIVE_FILE:-${1}}" | ||
| VORTEX_EXPORT_DB_IMAGE_ARCHIVE_FILE="${VORTEX_EXPORT_DB_IMAGE_ARCHIVE_FILE:-${1}}" | ||
|
|
||
| # Container image to store in a form of `<org>/<repository>`. | ||
| VORTEX_DB_EXPORT_IMAGE="${VORTEX_DB_EXPORT_IMAGE:-}" | ||
| VORTEX_EXPORT_DB_IMAGE="${VORTEX_EXPORT_DB_IMAGE:-}" | ||
|
|
||
| # Container registry name. | ||
| VORTEX_DB_EXPORT_CONTAINER_REGISTRY="${VORTEX_DB_EXPORT_CONTAINER_REGISTRY:-${VORTEX_CONTAINER_REGISTRY:-docker.io}}" | ||
| VORTEX_EXPORT_DB_CONTAINER_REGISTRY="${VORTEX_EXPORT_DB_CONTAINER_REGISTRY:-${VORTEX_CONTAINER_REGISTRY:-docker.io}}" | ||
|
|
||
| # The service name to capture. | ||
| VORTEX_DB_EXPORT_SERVICE_NAME="${VORTEX_DB_EXPORT_SERVICE_NAME:-database}" | ||
| VORTEX_EXPORT_DB_SERVICE_NAME="${VORTEX_EXPORT_DB_SERVICE_NAME:-database}" | ||
|
|
||
| # Directory with database image archive file. | ||
| VORTEX_DB_EXPORT_IMAGE_DIR="${VORTEX_DB_EXPORT_IMAGE_DIR:-${VORTEX_DB_DIR}}" | ||
| VORTEX_EXPORT_DB_IMAGE_DIR="${VORTEX_EXPORT_DB_IMAGE_DIR:-${VORTEX_DB_DIR}}" |
There was a problem hiding this comment.
Avoid changing scripts/vortex directly.
Repo guidance says custom script changes must live under scripts/custom/. Please move these edits there or confirm this is an intentional core template change.
As per coding guidelines: "scripts/**/*.{sh,php,js}: Never modify scripts/vortex/ - use scripts/custom/ for custom scripts".
🤖 Prompt for AI Agents
In `@scripts/vortex/export-db-image.sh` around lines 14 - 27, You modified the
core vortex export script variables (VORTEX_EXPORT_DB_IMAGE_ARCHIVE_FILE,
VORTEX_EXPORT_DB_IMAGE, VORTEX_EXPORT_DB_CONTAINER_REGISTRY,
VORTEX_EXPORT_DB_SERVICE_NAME, VORTEX_EXPORT_DB_IMAGE_DIR); per repo guidelines
these changes must not live in the core scripts directory—move the edited logic
into a new script under the custom scripts area (preserve the same variable
names and behavior) and revert the edits to the original core script, or if this
is an intentional template change, add a clear justification in the PR
description and request owner approval.
This comment has been minimized.
This comment has been minimized.
|
|
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #2265 +/- ##
==========================================
- Coverage 77.05% 76.44% -0.61%
==========================================
Files 114 107 -7
Lines 5988 5829 -159
Branches 44 0 -44
==========================================
- Hits 4614 4456 -158
+ Misses 1374 1373 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
AlexSkrypnyk
force-pushed
the
feature/update-vars-scripts
branch
from
0f71e15 to
0b9ed5f
Compare
|
|
There was a problem hiding this comment.
Actionable comments posted: 4
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (4)
scripts/vortex/download-db-s3.sh (1)
16-116:⚠️ Potential issue | 🟠 MajorDo not modify
scripts/vortex/directly.These edits change a script under
scripts/vortex/. Please move the customization intoscripts/custom/(or adjust the guideline if this is intended core change).As per coding guidelines, "Never modify
scripts/vortex/- usescripts/custom/for custom scripts".scripts/vortex/download-db-acquia.sh (1)
37-263:⚠️ Potential issue | 🟠 MajorDo not modify
scripts/vortex/directly.These edits change a script under
scripts/vortex/. Please move the customization intoscripts/custom/(or adjust the guideline if this is intended core change).As per coding guidelines, "Never modify
scripts/vortex/- usescripts/custom/for custom scripts".scripts/vortex/download-db-lagoon.sh (1)
25-129:⚠️ Potential issue | 🟠 MajorDo not modify
scripts/vortex/directly.These edits change a script under
scripts/vortex/. Please move the customization intoscripts/custom/(or adjust the guideline if this is intended core change).As per coding guidelines, "Never modify
scripts/vortex/- usescripts/custom/for custom scripts".scripts/vortex/upload-db-s3.sh (1)
16-136:⚠️ Potential issue | 🟠 MajorGuideline violation: changes in
scripts/vortex/.Repository rules say customizations must live in
scripts/custom/, notscripts/vortex/. Please relocate these changes to a custom script (and update callers/docs accordingly), or confirm and update the guideline if this is intended as a core change.As per coding guidelines, “scripts/**/*.{sh,php,js}: Never modify scripts/vortex/ - use scripts/custom/ for custom scripts”.
🤖 Fix all issues with AI agents
In `@scripts/vortex/download-db.sh`:
- Around line 18-26: The three environment-variable edits
(VORTEX_DOWNLOAD_DB_SOURCE, VORTEX_DOWNLOAD_DB_FORCE,
VORTEX_DOWNLOAD_DB_PROCEED) must not be made in the core vortex script; instead
move them into your project’s custom scripts by creating a small custom wrapper
that exports these variables and then invokes the original vortex download logic
(or update the guideline if this is intended as a core change). Locate the added
variables in the modified download script (VORTEX_DOWNLOAD_DB_SOURCE,
VORTEX_DOWNLOAD_DB_FORCE, VORTEX_DOWNLOAD_DB_PROCEED) and remove them from the
core file, placing equivalent export lines in the custom wrapper so core scripts
remain unchanged.
- Line 39: The user-facing message still references the old env var name; update
the message in the conditional that begins with [
"${VORTEX_DOWNLOAD_DB_PROCEED}" != "1" ] so it mentions
VORTEX_DOWNLOAD_DB_PROCEED (not DB_DOWNLOAD_PROCEED) — change the string passed
to pass() to reflect the renamed variable and keep the rest of the conditional
logic unchanged.
In `@scripts/vortex/export-db-file.sh`:
- Line 13: The change to the core script setting VORTEX_EXPORT_DB_FILE_DIR (the
line defining
VORTEX_EXPORT_DB_FILE_DIR="${VORTEX_EXPORT_DB_FILE_DIR:-${VORTEX_DB_DIR:-./.data}}")
must not be made directly under scripts/vortex; instead move your customizations
into a new script under scripts/custom/ (or update an existing custom script)
and source or override the variable there, leaving the core file untouched;
ensure any other edits you made in the same area (lines referencing
VORTEX_DB_DIR or related defaults) are replicated in your custom script so the
runtime picks up the override without modifying scripts/vortex.
In `@scripts/vortex/export-db.sh`:
- Line 44: The change modifies a core script under the vortex scripts tree by
adding a call to export-db-image.sh via VORTEX_EXPORT_DB_IMAGE which violates
the rule to never edit scripts/vortex/*; revert this edit in the core script and
instead create a new custom wrapper under scripts/custom (e.g., a new
export-db.sh) that sets VORTEX_EXPORT_DB_IMAGE and invokes export-db-image.sh,
and update any internal invocations or documentation to point to the new
scripts/custom wrapper; look for the symbol VORTEX_EXPORT_DB_IMAGE and the
invocation of export-db-image.sh to locate the exact behavior to duplicate into
the custom script and remove from the core one.
| VORTEX_DOWNLOAD_DB_SOURCE="${VORTEX_DOWNLOAD_DB_SOURCE:-url}" | ||
|
|
||
| # Force DB download even if the cache exists. | ||
| # Usually set in CircleCI UI to override per build cache. | ||
| VORTEX_DB_DOWNLOAD_FORCE="${VORTEX_DB_DOWNLOAD_FORCE:-}" | ||
| VORTEX_DOWNLOAD_DB_FORCE="${VORTEX_DOWNLOAD_DB_FORCE:-}" | ||
|
|
||
| # Proceed with download. | ||
| VORTEX_DB_DOWNLOAD_PROCEED="${VORTEX_DB_DOWNLOAD_PROCEED:-1}" | ||
| VORTEX_DOWNLOAD_DB_PROCEED="${VORTEX_DOWNLOAD_DB_PROCEED:-1}" | ||
|
|
There was a problem hiding this comment.
Do not modify scripts/vortex/ directly.
These edits change a script under scripts/vortex/. Please move the customization into scripts/custom/ (or adjust the guideline if this is intended core change).
As per coding guidelines, "Never modify scripts/vortex/ - use scripts/custom/ for custom scripts".
🤖 Prompt for AI Agents
In `@scripts/vortex/download-db.sh` around lines 18 - 26, The three
environment-variable edits (VORTEX_DOWNLOAD_DB_SOURCE, VORTEX_DOWNLOAD_DB_FORCE,
VORTEX_DOWNLOAD_DB_PROCEED) must not be made in the core vortex script; instead
move them into your project’s custom scripts by creating a small custom wrapper
that exports these variables and then invokes the original vortex download logic
(or update the guideline if this is intended as a core change). Locate the added
variables in the modified download script (VORTEX_DOWNLOAD_DB_SOURCE,
VORTEX_DOWNLOAD_DB_FORCE, VORTEX_DOWNLOAD_DB_PROCEED) and remove them from the
core file, placing equivalent export lines in the custom wrapper so core scripts
remain unchanged.
| info "Started database download." | ||
|
|
||
| [ "${VORTEX_DB_DOWNLOAD_PROCEED}" != "1" ] && pass "Skipping database download as DB_DOWNLOAD_PROCEED is not set to 1." && exit 0 | ||
| [ "${VORTEX_DOWNLOAD_DB_PROCEED}" != "1" ] && pass "Skipping database download as DB_DOWNLOAD_PROCEED is not set to 1." && exit 0 |
There was a problem hiding this comment.
Fix the user-facing message to the renamed variable.
Line 39 still references DB_DOWNLOAD_PROCEED, which no longer matches the env var name.
🛠️ Proposed fix
-[ "${VORTEX_DOWNLOAD_DB_PROCEED}" != "1" ] && pass "Skipping database download as DB_DOWNLOAD_PROCEED is not set to 1." && exit 0
+[ "${VORTEX_DOWNLOAD_DB_PROCEED}" != "1" ] && pass "Skipping database download as VORTEX_DOWNLOAD_DB_PROCEED is not set to 1." && exit 0📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| [ "${VORTEX_DOWNLOAD_DB_PROCEED}" != "1" ] && pass "Skipping database download as DB_DOWNLOAD_PROCEED is not set to 1." && exit 0 | |
| [ "${VORTEX_DOWNLOAD_DB_PROCEED}" != "1" ] && pass "Skipping database download as VORTEX_DOWNLOAD_DB_PROCEED is not set to 1." && exit 0 |
🤖 Prompt for AI Agents
In `@scripts/vortex/download-db.sh` at line 39, The user-facing message still
references the old env var name; update the message in the conditional that
begins with [ "${VORTEX_DOWNLOAD_DB_PROCEED}" != "1" ] so it mentions
VORTEX_DOWNLOAD_DB_PROCEED (not DB_DOWNLOAD_PROCEED) — change the string passed
to pass() to reflect the renamed variable and keep the rest of the conditional
logic unchanged.
|
|
||
| # Directory with database dump file. | ||
| VORTEX_DB_EXPORT_FILE_DIR="${VORTEX_DB_EXPORT_FILE_DIR:-${VORTEX_DB_DIR:-./.data}}" | ||
| VORTEX_EXPORT_DB_FILE_DIR="${VORTEX_EXPORT_DB_FILE_DIR:-${VORTEX_DB_DIR:-./.data}}" |
There was a problem hiding this comment.
Avoid editing core scripts/vortex directly.
These edits should live under scripts/custom/ unless this is an intentional core template change with explicit approval.
As per coding guidelines: "scripts/**/*.{sh,php,js}: Never modify scripts/vortex/ - use scripts/custom/ for custom scripts".
Also applies to: 31-31, 39-39
🤖 Prompt for AI Agents
In `@scripts/vortex/export-db-file.sh` at line 13, The change to the core script
setting VORTEX_EXPORT_DB_FILE_DIR (the line defining
VORTEX_EXPORT_DB_FILE_DIR="${VORTEX_EXPORT_DB_FILE_DIR:-${VORTEX_DB_DIR:-./.data}}")
must not be made directly under scripts/vortex; instead move your customizations
into a new script under scripts/custom/ (or update an existing custom script)
and source or override the variable there, leaving the core file untouched;
ensure any other edits you made in the same area (lines referencing
VORTEX_DB_DIR or related defaults) are replicated in your custom script so the
runtime picks up the override without modifying scripts/vortex.
| else | ||
| # Export database as a container image. | ||
| VORTEX_DB_EXPORT_IMAGE="${VORTEX_DB_IMAGE}" ./scripts/vortex/export-db-image.sh "$@" | ||
| VORTEX_EXPORT_DB_IMAGE="${VORTEX_DB_IMAGE}" ./scripts/vortex/export-db-image.sh "$@" |
There was a problem hiding this comment.
Avoid editing core scripts/vortex directly.
These edits should live under scripts/custom/ unless this is an intentional core template change with explicit approval.
As per coding guidelines: "scripts/**/*.{sh,php,js}: Never modify scripts/vortex/ - use scripts/custom/ for custom scripts".
🤖 Prompt for AI Agents
In `@scripts/vortex/export-db.sh` at line 44, The change modifies a core script
under the vortex scripts tree by adding a call to export-db-image.sh via
VORTEX_EXPORT_DB_IMAGE which violates the rule to never edit scripts/vortex/*;
revert this edit in the core script and instead create a new custom wrapper
under scripts/custom (e.g., a new export-db.sh) that sets VORTEX_EXPORT_DB_IMAGE
and invokes export-db-image.sh, and update any internal invocations or
documentation to point to the new scripts/custom wrapper; look for the symbol
VORTEX_EXPORT_DB_IMAGE and the invocation of export-db-image.sh to locate the
exact behavior to duplicate into the custom script and remove from the core one.
|
|
1 participant
Summary
Fixed inconsistent variable name prefixes in
scripts/vortex/so that eachvariable prefix matches its script filename (hyphens to underscores, uppercased).
Three prefix patterns had the word order swapped (
DBappeared before the actioninstead of after).
.envfiles, CI configs, docs, PHPinstaller code, ahoy/lagoon configs, installer test fixtures)
Variables renamed
download-db.shVORTEX_DB_DOWNLOAD_SOURCEVORTEX_DOWNLOAD_DB_SOURCEdownload-db.shVORTEX_DB_DOWNLOAD_FORCEVORTEX_DOWNLOAD_DB_FORCEdownload-db.shVORTEX_DB_DOWNLOAD_PROCEEDVORTEX_DOWNLOAD_DB_PROCEEDdownload-db.shVORTEX_DB_DOWNLOAD_SEMAPHOREVORTEX_DOWNLOAD_DB_SEMAPHOREdownload-db-acquia.shVORTEX_DB_DOWNLOAD_ENVIRONMENTVORTEX_DOWNLOAD_DB_ENVIRONMENTdownload-db-acquia.shVORTEX_DB_DOWNLOAD_ACQUIA_DB_NAMEVORTEX_DOWNLOAD_DB_ACQUIA_DB_NAMEdownload-db-acquia.shVORTEX_DB_DOWNLOAD_FRESHVORTEX_DOWNLOAD_DB_FRESHdownload-db-acquia.shVORTEX_DB_DOWNLOAD_ACQUIA_BACKUP_WAIT_INTERVALVORTEX_DOWNLOAD_DB_ACQUIA_BACKUP_WAIT_INTERVALdownload-db-acquia.shVORTEX_DB_DOWNLOAD_ACQUIA_BACKUP_MAX_WAITVORTEX_DOWNLOAD_DB_ACQUIA_BACKUP_MAX_WAITdownload-db-ftp.shVORTEX_DB_DOWNLOAD_FTP_USERVORTEX_DOWNLOAD_DB_FTP_USERdownload-db-ftp.shVORTEX_DB_DOWNLOAD_FTP_PASSVORTEX_DOWNLOAD_DB_FTP_PASSdownload-db-ftp.shVORTEX_DB_DOWNLOAD_FTP_HOSTVORTEX_DOWNLOAD_DB_FTP_HOSTdownload-db-ftp.shVORTEX_DB_DOWNLOAD_FTP_PORTVORTEX_DOWNLOAD_DB_FTP_PORTdownload-db-ftp.shVORTEX_DB_DOWNLOAD_FTP_FILEVORTEX_DOWNLOAD_DB_FTP_FILEdownload-db-lagoon.shVORTEX_DB_DOWNLOAD_FRESHVORTEX_DOWNLOAD_DB_FRESHdownload-db-lagoon.shVORTEX_DB_DOWNLOAD_ENVIRONMENTVORTEX_DOWNLOAD_DB_ENVIRONMENTdownload-db-lagoon.shVORTEX_DB_DOWNLOAD_LAGOON_REMOTE_DIRVORTEX_DOWNLOAD_DB_LAGOON_REMOTE_DIRdownload-db-lagoon.shVORTEX_DB_DOWNLOAD_LAGOON_REMOTE_FILEVORTEX_DOWNLOAD_DB_LAGOON_REMOTE_FILEdownload-db-lagoon.shVORTEX_DB_DOWNLOAD_LAGOON_REMOTE_FILE_CLEANUPVORTEX_DOWNLOAD_DB_LAGOON_REMOTE_FILE_CLEANUPdownload-db-lagoon.shVORTEX_DB_DOWNLOAD_SSH_FINGERPRINTVORTEX_DOWNLOAD_DB_SSH_FINGERPRINTdownload-db-lagoon.shVORTEX_DB_DOWNLOAD_SSH_FILEVORTEX_DOWNLOAD_DB_SSH_FILEdownload-db-lagoon.shVORTEX_DB_DOWNLOAD_LAGOON_SSH_HOSTVORTEX_DOWNLOAD_DB_LAGOON_SSH_HOSTdownload-db-lagoon.shVORTEX_DB_DOWNLOAD_LAGOON_SSH_PORTVORTEX_DOWNLOAD_DB_LAGOON_SSH_PORTdownload-db-lagoon.shVORTEX_DB_DOWNLOAD_LAGOON_SSH_USERVORTEX_DOWNLOAD_DB_LAGOON_SSH_USERdownload-db-s3.shVORTEX_DB_DOWNLOAD_S3_ACCESS_KEYVORTEX_DOWNLOAD_DB_S3_ACCESS_KEYdownload-db-s3.shVORTEX_DB_DOWNLOAD_S3_SECRET_KEYVORTEX_DOWNLOAD_DB_S3_SECRET_KEYdownload-db-s3.shVORTEX_DB_DOWNLOAD_S3_BUCKETVORTEX_DOWNLOAD_DB_S3_BUCKETdownload-db-s3.shVORTEX_DB_DOWNLOAD_S3_REGIONVORTEX_DOWNLOAD_DB_S3_REGIONdownload-db-s3.shVORTEX_DB_DOWNLOAD_S3_PREFIXVORTEX_DOWNLOAD_DB_S3_PREFIXdownload-db-url.shVORTEX_DB_DOWNLOAD_URLVORTEX_DOWNLOAD_DB_URLdownload-db-url.shVORTEX_DB_DOWNLOAD_UNZIP_PASSWORDVORTEX_DOWNLOAD_DB_UNZIP_PASSWORDexport-db.shVORTEX_DB_EXPORT_IMAGEVORTEX_EXPORT_DB_IMAGEexport-db-file.shVORTEX_DB_EXPORT_FILE_DIRVORTEX_EXPORT_DB_FILE_DIRexport-db-image.shVORTEX_DB_EXPORT_IMAGE_ARCHIVE_FILEVORTEX_EXPORT_DB_IMAGE_ARCHIVE_FILEexport-db-image.shVORTEX_DB_EXPORT_IMAGEVORTEX_EXPORT_DB_IMAGEexport-db-image.shVORTEX_DB_EXPORT_CONTAINER_REGISTRYVORTEX_EXPORT_DB_CONTAINER_REGISTRYexport-db-image.shVORTEX_DB_EXPORT_SERVICE_NAMEVORTEX_EXPORT_DB_SERVICE_NAMEexport-db-image.shVORTEX_DB_EXPORT_IMAGE_DIRVORTEX_EXPORT_DB_IMAGE_DIRupload-db-s3.shVORTEX_DB_UPLOAD_S3_ACCESS_KEYVORTEX_UPLOAD_DB_S3_ACCESS_KEYupload-db-s3.shVORTEX_DB_UPLOAD_S3_SECRET_KEYVORTEX_UPLOAD_DB_S3_SECRET_KEYupload-db-s3.shVORTEX_DB_UPLOAD_S3_BUCKETVORTEX_UPLOAD_DB_S3_BUCKETupload-db-s3.shVORTEX_DB_UPLOAD_S3_REGIONVORTEX_UPLOAD_DB_S3_REGIONupload-db-s3.shVORTEX_DB_UPLOAD_S3_PREFIXVORTEX_UPLOAD_DB_S3_PREFIXupload-db-s3.shVORTEX_DB_UPLOAD_S3_REMOTE_FILEVORTEX_UPLOAD_DB_S3_REMOTE_FILEupload-db-s3.shVORTEX_DB_UPLOAD_S3_STORAGE_CLASSVORTEX_UPLOAD_DB_S3_STORAGE_CLASSSummary by CodeRabbit