Skip to content

Conversation

@carlbrugger
Copy link
Contributor

Fixes the CLI deploy command's incomplete handling of the --ci flag.

Problem

The namespace prompt in the deploy command was not respecting the --ci flag, causing CI pipelines to hang when:

  • No namespace was provided via --namespace option
  • No FLATFILE_AGENT_NAMESPACE environment variable was set
  • No existing agent was selected

Solution

Added a check for the --ci flag in the namespace prompt condition. Now the prompt is skipped in CI mode, preventing pipeline blocking.

Changes

  • Updated deploy.action.ts to check options?.ci before showing namespace prompt
  • Added changeset documenting the fix

Testing

The fix ensures that in CI mode, the deploy command will proceed without interactive prompts for namespace input.

Prevents CI pipelines from hanging on interactive namespace input when
no namespace is provided via options or environment variables.

Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-e49789ac-7df6-4ae9-a3f6-11b7739ad3f5
@promptless
Copy link

promptless bot commented Aug 28, 2025

📝 Documentation updates detected!

New suggestion: Document CLI deploy command --ci flag bug fix in libraries changelog

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