Skip to content

Comments

Deploy new project#1258

Merged
josephjclark merged 6 commits intorelease/nextfrom
deploy-new
Feb 17, 2026
Merged

Deploy new project#1258
josephjclark merged 6 commits intorelease/nextfrom
deploy-new

Conversation

@josephjclark
Copy link
Collaborator

Short Description

Allow a new project to be deployed to a lightning instance with --new

This basically means skipping all the merge logic in the CLI - just post the checked out project verbatim. The CLI will generate UUIDs for the new project.

Superuser privileges are required on the API key to create a new project.

A name can be be passed if you want to overwrite the OG name. Deploy wherever you like with the usual arguments

Fixes #1255

AI Usage

Please disclose whether you've used AI anywhere in this PR (it's cool, we just
want to know!):

  • I have used Claude Code
  • I have used another model
  • I have not used AI

You can read more details in our
Responsible AI Policy

@github-project-automation github-project-automation bot moved this to New Issues in v2 Feb 17, 2026
@josephjclark josephjclark changed the base branch from main to release/next February 17, 2026 13:46
@josephjclark josephjclark merged commit 92c0b49 into release/next Feb 17, 2026
6 checks passed
@github-project-automation github-project-automation bot moved this from New Issues to Done in v2 Feb 17, 2026
@josephjclark josephjclark deleted the deploy-new branch February 17, 2026 19:03
josephjclark added a commit that referenced this pull request Feb 17, 2026
* Handle missing source in sourcemap gracefully (#1250)

* Handle missing source in sourcemap gracefully

Use the returnNullOnMissing parameter of sourceContentFor to avoid
throwing when the source file isn't in the sourcemap (e.g. when no
adaptor is provided).

See #1249

* Trigger CI re-run

* changeset

* Validate API key and endpoint before making requests (#1251)

* Validate API key and endpoint before making requests

Throw a clear error when OPENFN_API_KEY or OPENFN_ENDPOINT is missing
instead of letting it fall through to a cryptic TypeError: Invalid URL.

See #1249

* Move endpoint validation to getLightningUrl

The endpoint can come from the local project file (not just env/CLI
args), so validating in loadAppAuthConfig is too early. Move the check
to getLightningUrl where the endpoint is actually consumed.

* default endpoint

* changelog

* Deploy new project (#1258)

* project: allow project name to be overriden when loading from fs

* slugify project name

* add --new flag to deploy to enable a new project to be created

* fix local  aliasing

* remove .only

* update test

* versions: cli@1.27.0 worker@1.21.4

---------

Co-authored-by: Elias Waly Ba <eliaswalyba@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

CLI deploy: allow an new project to be created

1 participant