You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
At present, there are a small number of methods in the Upstream API that are not in the flux API. These are methods that can be called via RPC from an upstream (i.e., Weave Cloud) connection, but not via HTTP (e.g., not by fluxctl).
In the course of separating the Upstream part of the daemon out into weaveworks/flux-adapter, these will have to move into the public API, since flux-adapter runs in a sidecar, and uses HTTP (via http/client) rather than having in-process access to the daemon.
I believe the upstream methods can just be added to the v11 Server interface, and the Upstream interface abandoned from now on.
The text was updated successfully, but these errors were encountered:
At present, there are a small number of methods in the Upstream API that are not in the flux API. These are methods that can be called via RPC from an upstream (i.e., Weave Cloud) connection, but not via HTTP (e.g., not by
fluxctl
).In the course of separating the Upstream part of the daemon out into weaveworks/flux-adapter, these will have to move into the public API, since
flux-adapter
runs in a sidecar, and uses HTTP (via http/client) rather than having in-process access to the daemon.I believe the upstream methods can just be added to the v11 Server interface, and the Upstream interface abandoned from now on.
The text was updated successfully, but these errors were encountered: