zitadel/apps/api/cmd/setup/39.sql

DELETE FROM eventstore.fields
WHERE aggregate_type = 'org'
AND aggregate_id IN (
	SELECT aggregate_id
	FROM eventstore.events2
	WHERE instance_id = $1
	AND aggregate_type = 'org'
	AND event_type = 'org.removed'
);
fix(eventstore): cleanup org fields on remove (#8946) # Which Problems Are Solved When an org is removed, the corresponding fields are not deleted. This creates issues, such as recreating a new org with the same verified domain. # How the Problems Are Solved Remove the search fields by the org aggregate, instead of just setting the removed state. # Additional Changes - Cleanup migration script that removed current stale fields. # Additional Context - Closes https://github.com/zitadel/zitadel/issues/8943 - Related to https://github.com/zitadel/zitadel/pull/8790 --------- Co-authored-by: Silvan <silvan.reusser@gmail.com> 2024-11-26 17:26:41 +02:00			`DELETE FROM eventstore.fields`
			`WHERE aggregate_type = 'org'`
fix(migrations): clean stale org fields using events (#9051) # 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 2024-12-12 18:37:18 +02:00			`AND aggregate_id IN (`
			`SELECT aggregate_id`
			`FROM eventstore.events2`
fix(setup): make step 39 repeatable (#9085) # Which Problems Are Solved When downgrading zitadel and upgrading it again, it might be that orgs deleted in this period still have stale entries in the fields table. # How the Problems Are Solved - Make the cleanup repeatable - Scope the query by instance so that an index is used. 2024-12-18 17:48:22 +02:00			`WHERE instance_id = $1`
			`AND aggregate_type = 'org'`
fix(migrations): clean stale org fields using events (#9051) # 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 2024-12-12 18:37:18 +02:00			`AND event_type = 'org.removed'`
fix(eventstore): cleanup org fields on remove (#8946) # Which Problems Are Solved When an org is removed, the corresponding fields are not deleted. This creates issues, such as recreating a new org with the same verified domain. # How the Problems Are Solved Remove the search fields by the org aggregate, instead of just setting the removed state. # Additional Changes - Cleanup migration script that removed current stale fields. # Additional Context - Closes https://github.com/zitadel/zitadel/issues/8943 - Related to https://github.com/zitadel/zitadel/pull/8790 --------- Co-authored-by: Silvan <silvan.reusser@gmail.com> 2024-11-26 17:26:41 +02:00			`);`