Skip to content

Conversation

@hrishikesh-k
Copy link

Description

This PR instroduces support for setting environment variables for settings configured in manifest instead off relying on interactive shells. The reason is to support a use-case as follows:

I'm using Vue + Vite to develop a Zendesk App. I have configured some scripts in my package.json as follows:

{
  "scripts": {
    "build": "dotenv -- npm-run-all lint typecheck build:vite build:zd",
    "build:vite": "vite build",
    "build:zd": "zcli apps:package ./dist/",
    "dev": "dotenv -- npm-run-all --parallel \"build:vite -- --emptyOutDir false --watch\" dev:zd",
    "dev:vite": "vite dev",
    "dev:zd": "zcli apps:server ./dist/",
    "lint": "biome check",
    "typecheck": "vue-tsc --noEmit"
  }
}

So far, I was just running npm run dev and it was all working fine for me from a single shell. However, then I introduced a secure setting which now prompts me to enter some text when I run zcli apps:server. Since I'm running this with npm-run-all, I never get a chance to enter my text and the script fails.

Instead, if the value can be set from environment variables, that would solve the issue.

Do NOT write here! This section will be filled in by GitHub Action
automatically. If you don't want this, either remove the markers or write
outside the fences.

Checklist

  • 💂‍♂️ includes new unit and functional tests

@hrishikesh-k hrishikesh-k requested a review from a team as a code owner September 17, 2025 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant