feat(raptor-register): a raptor action to replace facetsctl-register

[anujhydrabadi]

facetsctl-register is a Docker action on docker://facetscloud/facetsctl:latest running facetsctl v2 — the legacy write path, which registers a build with no routing rule attached. It is also broken as written: it reads secrets.* from inside the action, which is not a context an action can read, so its credentials arrive empty. It is deprecated here rather than fixed.

raptor-register is a composite action — raptor publishes no image, so there is nothing to run a Docker action on.

- uses: Facets-cloud/github-actions/raptor-register@v1with:
control_plane_url: ${{ secrets.FACETS_CP_URL }}username: ${{ secrets.FACETS_USERNAME }}token: ${{ secrets.FACETS_TOKEN }}project: my-projectartifact: my-project-apiimage: my.registry.example.com/my-project/api:${{ github.sha }}git_ref: ${{ github.ref_name }}

The target is explicit

git_ref lets the project's routing rules place the build; environment and release_stream name the target outright. Exactly one is required — zero or two is an error, not something the action picks for the caller.

Two things it does not inherit

• Credentials are inputs, not an implicit read of secrets.*, and they are scoped to the single step that invokes raptor — so the token is not exported into the rest of the caller's job. (Same pattern as module-ci-action.)
• registration_type, registry and description are gone. The first is implied by which target input you pass; the second is wherever you pushed, which image already names; the third is not carried on a build registration.

The README maps every old input to its replacement, and says where to read an artifact name from — it is the CI integration, not the resource, and the two differ often enough to be worth stating (raptor get resources -p <project> -o wide, the ARTIFACT column).

Part of the facetsctl retirement.

🤖 Generated with Claude Code