Replies: 1 comment 4 replies
-
|
This is something we think we would consider in the scope of changes that might be possible for GA We want to be careful about creating new public API surfaces because right now we have the flexibility to change how the CLI works without breaking downstream consumers (the stability guarantees are not there for the CLI internals as I understand our current position, we're maintaining the capability to break things in there until we've declared general availability, then we will add some new stability guarantees...) More information about GA here: https://fluxcd.io/roadmap/#the-road-to-flux-v2-ga I think based on our discussion at Flux Bug Scrub about this today, this is something we will consider, but it is going to require some thought and can't be done right away. If you can tell us what you need it for with a bit of specificity, we can perhaps point you to the Flux functionality in the relevant package so you can use it from the APIs which are already exposed and considered as stable? For example, all of the new OCI functionality is supposed to be exposed in packages already. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Simple making the changes I made in this fork to make it possible to embed the flux command like kubectl can be embedded.
This makes it possible for people to vendor complete cli toolkits.
Beta Was this translation helpful? Give feedback.
All reactions