Kasper Juul Hermansen 1793d8b29c
All checks were successful
continuous-integration/drone/pr Build is passing
continuous-integration/drone/push Build is passing
fix(deps): update rust crate uuid to v1.13.1
2025-02-06 01:38:36 +00:00
2024-02-18 01:29:46 +01:00
2024-05-26 15:19:58 +02:00
2024-09-08 12:45:20 +02:00
2024-02-21 06:51:54 +01:00
2024-02-10 22:01:28 +01:00
2024-09-08 12:49:36 +02:00
2024-02-18 01:29:46 +01:00
2024-03-09 21:48:58 +00:00

Flux releaser

Usage

mkdir -p some/path

mkdir -p some/path/someEnvironment
touch some/path/someEnvironment/someFile.txt

# Should be run from a ci pipeline

flux-releaser commit \
  --app someApp \
  --branch someBranch \
  --include some/path \
  --registry https://flux-releaser.i.kjuulh.io

!!! note include path should include a sub folder for each releaseable artifact

flux releaser can also be used as a library, which is especially useful if integrated with dagger

Now you can release or auto-release this your desired environment and app

flux-releaser release \
  --app someApp \
  --branch someBranch \
  --registry https://flux-releaser.i.kjuulh.io

If cuddle.yaml is available it will automatically include required information from its references

flux-releaser release --branch someBranch

Install

Client & CI

Flux releaser is a rust app used client side and in CI as a cli app (flux-releaser), or alternatively as a rust library.

Registry

Flux releaser requires a server to function. Said flux is packaged in a helm chart, and is available at tbd, if the helm chart is used, it will stand-up a cockroach cluster and minio for artifacts.

Flux releaser also requires a connection to a flux gitops registry. This is provided to the flux app on the server via. a toml file (see configuration), but the defaults should work fine.

Description
No description provided
Readme 1.1 MiB
Languages
Rust 100%