zitadel/cmd
Silvan 17953e9040
fix(setup): init projections (#7194)
Even though this is a feature it's released as fix so that we can back port to earlier revisions.

As reported by multiple users startup of ZITADEL after leaded to downtime and worst case rollbacks to the previously deployed version.

The problem starts rising when there are too many events to process after the start of ZITADEL. The root cause are changes on projections (database tables) which must be recomputed. This PR solves this problem by adding a new step to the setup phase which prefills the projections. The step can be enabled by adding the `--init-projections`-flag to `setup`, `start-from-init` and `start-from-setup`. Setting this flag results in potentially longer duration of the setup phase but reduces the risk of the problems mentioned in the paragraph above.
2024-01-25 17:28:20 +01:00
..
admin chore: test server for direct resource access 2023-04-24 20:40:31 +03:00
build fix: allow version to be overwritten by build again (#4656) 2022-11-07 09:50:44 +00:00
encryption fix(setup): init projections (#7194) 2024-01-25 17:28:20 +01:00
initialise feat: block instances (#7129) 2024-01-17 10:16:48 +00:00
key fix(db): always use begin tx (#7142) 2024-01-04 16:12:20 +00:00
ready feat: improve UX for external configuration (#6861) 2023-11-09 11:30:15 +01:00
setup fix(setup): init projections (#7194) 2024-01-25 17:28:20 +01:00
start fix(setup): init projections (#7194) 2024-01-25 17:28:20 +01:00
systemapi fix(setup): init projections (#7194) 2024-01-25 17:28:20 +01:00
tls fix: enable env vars in setup steps (and deprecate admin subcommand) (#3871) 2022-06-27 10:32:34 +00:00
defaults.yaml fix(setup): init projections (#7194) 2024-01-25 17:28:20 +01:00
zitadel.go ci: improve performance (#5953) 2023-07-17 10:08:20 +02:00