Install fda, the Feldera CLI, from
GitHub releases and put it on PATH.
- uses: feldera/fda-install-action@<sha> # v1.0.0
with:
version: 0.327.0
- run: fda pipelines| Input | Default | Meaning |
|---|---|---|
version |
latest |
Release to install, with or without a leading v. latest resolves the newest release of feldera/feldera. |
| Output | Contents |
|---|---|
version |
The release that was installed, without the leading v |
path |
Directory the binary was installed into |
fda is published for four targets, and the action installs the one matching
the runner:
| Runner | Target |
|---|---|
| Linux x64 | x86_64-unknown-linux-gnu |
| Linux arm64 | aarch64-unknown-linux-gnu |
| macOS arm64 | aarch64-apple-darwin |
| Windows x64 | x86_64-pc-windows-msvc |
Anything else fails the step naming the runner, rather than downloading
something that cannot run. macOS x64 (macos-13 and earlier) and Windows arm64
have no published build.
Pin the SHA and let Dependabot move it, as with any third-party action:
- uses: feldera/fda-install-action@<sha> # v1.0.0Pinning version is worth doing separately. latest follows whatever
feldera/feldera released most recently, so a job that pins the action but not
the CLI still changes underneath you.
The binary lands in the runner tool cache under
fda/<version>/<target>, so a second use in the same job costs nothing.
No token is needed or accepted. latest is read from the redirect that
/releases/latest serves, and the assets are public, so nothing here is subject
to an API rate limit or to a job token that another repository's API refuses.
Releases publish no checksums, so the action does not verify one. It downloads
over HTTPS from github.com and confirms the binary runs before adding it to
PATH.