Mirrors/flux2
1
0
Fork 0
mirror of synced 2026-04-02 22:06:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add plugin authors responsibilities

Browse Source 
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
This commit is contained in:
Stefan Prodan
2026-04-01 14:27:09 +03:00
parent 8ac91c49e4
commit cf95179322
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
rfcs/xxxx-cli-plugin-system/README.md
View File

@@ -4,7 +4,7 @@
**Creation date:** 2026-03-30 **Creation date:** 2026-03-30
**Last update:** 2026-03-30 **Last update:** 2026-04-01
## Summary ## Summary
@@ -112,6 +112,10 @@ versions:
arch: amd64 arch: amd64
url: https://github.com/.../flux-operator_0.45.0_linux_amd64.tar.gz url: https://github.com/.../flux-operator_0.45.0_linux_amd64.tar.gz
checksum: sha256:96198da969096... checksum: sha256:96198da969096...
- os: windows
arch: amd64
url: https://github.com/.../flux-operator_0.45.0_windows_amd64.zip
checksum: sha256:9712026094a5...
``` ```
A generated `catalog.yaml` (`PluginCatalog` kind) contains static metadata for all A generated `catalog.yaml` (`PluginCatalog` kind) contains static metadata for all
@@ -218,6 +222,9 @@ Flux users can install it with `flux plugin install <name>`.
2. Submit a PR to `fluxcd/plugins` with `plugins/<name>.yaml` 2. Submit a PR to `fluxcd/plugins` with `plugins/<name>.yaml`
3. Subsequent releases are picked up by automated polling workflows 3. Subsequent releases are picked up by automated polling workflows
Plugin authors are responsible for maintaining their plugin definitions in the catalog,
by responding to issues and approving PRs for updates.
### Alternatives ### Alternatives
#### PATH-based Discovery (kubectl model) #### PATH-based Discovery (kubectl model)
@@ -296,6 +303,7 @@ The `fluxcd/plugins` repository includes CI workflows that:
checksum verification, binary presence in archives, no builtin collisions) checksum verification, binary presence in archives, no builtin collisions)
2. Regenerate `catalog.yaml` when plugins are added or removed 2. Regenerate `catalog.yaml` when plugins are added or removed
3. Automatically poll upstream repositories for new releases and create update PRs 3. Automatically poll upstream repositories for new releases and create update PRs
4. Plugin authors have to agree to maintain their plugin's definition by responding to issues and approving PRs in the catalog repo.
### Known Limitations (v1beta1) ### Known Limitations (v1beta1)