-
Notifications
You must be signed in to change notification settings - Fork 45
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
Introduce --production profile which disables --allow-bootstrap #2410
Comments
muhamadazmy
added a commit
to muhamadazmy/restate
that referenced
this issue
Jan 15, 2025
Summary: Support a `--production` flag that when enabled, overrides the default configuration with a production ready values So far the `--production` flag: - disables `allow-bootstrap` - sets the default provider to `replicated` Fixes restatedev#2410
muhamadazmy
added a commit
to muhamadazmy/restate
that referenced
this issue
Jan 17, 2025
Summary: Support a `--production` flag that when enabled, overrides the default configuration with a production ready values So far the `--production` flag: - disables `allow-bootstrap` - sets the default provider to `replicated` Fixes restatedev#2410
muhamadazmy
added a commit
to muhamadazmy/restate
that referenced
this issue
Jan 17, 2025
Summary: Support a `--production` flag that when enabled, overrides the default configuration with a production ready values So far the `--production` flag: - disables `allow-bootstrap` - sets the default provider to `replicated` Fixes restatedev#2410
muhamadazmy
added a commit
that referenced
this issue
Jan 17, 2025
Summary: Support a `--production` flag that when enabled, overrides the default configuration with a production ready values So far the `--production` flag: - disables `allow-bootstrap` - sets the default provider to `replicated` Fixes #2410
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To optimize the getting started experience, we set
--allow-bootstrap
when starting a Restate server by default. This is very convenient when running a single node Restate cluster or when trying Restate out locally. When deploying a multi node cluster this is problematic because when running with the embedded metadata store, we need one node to become the seed of the metadata store and not every node. Hence, we want to introduce a--production
profile that sets a few different default values for our configuration. One of them being that we don't--allow-bootstrap
and therefore require and explicit provision step (#2409).The text was updated successfully, but these errors were encountered: