[midigofrank]

Short Description

v2 of the deploy action, for Lightning's v2 GitHub sync. It deploys an openfn.yaml workspace with openfn project deploy instead of the legacy config.json + openfn deploy.

Implementation Details

• Inputs:
  • config_path_input is removed.
  • New project_id_input (required).
  • New endpoint_input, workspace_input and force_input (all optional).
• Runs openfn project deploy <project_id> --no-confirm, adding --endpoint and --force when those inputs are set.
• workspace_input is passed as OPENFN_WORKSPACE, so the project can live in a subfolder. It defaults to the repo root.
• Installs @openfn/cli@latest in its own step ("Install OpenFn CLI"), then deploys in "Deploy project to OpenFn" with --log info.
• Rewrote the README for v2. Repos on the old format should stay on @v1.

Release

This needs a v2 tag once merged. v1 stays as it is for legacy config.json repos.

QA Notes

• Tested end to end with Lightning's v2 sync (v2-github-actions branch), in both directions, at the repo root and in a workspace subfolder.
• Known CLI issues that show up through this action are tracked in kit: Fix: renaming a workflow in git deletes it in Lightning kit#1587, #1588, #1589.

[josephjclark]

Can we:
a) Put the node innstall into its own step (because its super noisy)
b) Give the cli step a nice name like "deploy project to openfn"

[josephjclark]

Can we add --log info here?

It might not make a lot of difference right now but I'd like to have the hook in place for richer output.

[midigofrank]

Done