Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow deploy time config #118

Open
Vaelatern opened this issue Jan 19, 2023 · 1 comment
Open

Allow deploy time config #118

Vaelatern opened this issue Jan 19, 2023 · 1 comment

Comments

@Vaelatern
Copy link

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?

@lispyclouds
Copy link
Member

There are the following issues to consider:

  • 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants