mirror of
https://github.com/zitadel/zitadel.git
synced 2024-12-15 12:27:59 +00:00
6f6e2234eb
# Which Problems Are Solved Migration step 39 is supposed to cleanup stale organization entries in the eventstore.fields table. In order to do this it used the projection to check which orgs still exist. During initial setup of ZITADEL the first instance with the organization is created. Howevet, the projections are filled after all migrations are done. With the organization projection empty, the fields of the first org would be deleted. This was discovered during development of a new field type. The accosiated events did not yet have any projection based filled assigned. It seems fields with a pre-fill projection are somehow restored. Therefore a restoration migration isn't required IMO. # How the Problems Are Solved Query the event store for `org.removed` events instead. This has the drawback of using a sequential scan on the eventstore, making the migration more expensive. # Additional Changes - none # Additional Context - Introduced in https://github.com/zitadel/zitadel/pull/8946 |
||
---|---|---|
.. | ||
admin | ||
build | ||
encryption | ||
hooks | ||
initialise | ||
key | ||
mirror | ||
ready | ||
setup | ||
start | ||
tls | ||
defaults.yaml | ||
zitadel.go |