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
Let's pretend we want to deploy bob fully formed. Can we have it load a config file on boot that has all the resources and everything else defined, without needing to start bob and poke the API a bunch?
The text was updated successfully, but these errors were encountered:
Bob is a distributed system and all of the state is stored on the XTDB.
The config here is essentially a state we'd like the DB to be in.
The only way to access the DB is via the apiserver and there is no API to set the state.
If the resource providers and artifat stores are known by Bob then they are expected to be reachable via the healthchecks. If by any chance those services are not up before Bob health checks start to fail til they are reachable.
This is analogous to a distributed system like kubernetes where the state needs to be formed up via API calls as well and there is no one single config file which could be loaded. The loading is especially an issue as multiple nodes are starting up and there isn't a clear place where to put this file in.
One we possibly can do this is having an endpoint to set the cluster state and have the user make that call instead of multiple API calls. Making bob load a config file is quite hard as of now.
Let's pretend we want to deploy bob fully formed. Can we have it load a config file on boot that has all the resources and everything else defined, without needing to start bob and poke the API a bunch?
The text was updated successfully, but these errors were encountered: