mirror of
https://github.com/zitadel/zitadel.git
synced 2025-08-12 03:47:33 +00:00
8d020e56bb
# Which Problems Are Solved As an outcome of [this issue](https://github.com/zitadel/zitadel/issues/9599) we want to implement relational tables in Zitadel. For that we use new tables as a successor of the current tables used by Zitadel in `projections`, `auth` and `admin` schemas. The new logic is based on [this proposal](https://github.com/zitadel/zitadel/pull/9870). This issue does not contain the switch from CQRS to the new tables. This is change will be implemented in a later stage. We focus on the most critical tables which is user authentication. We need a table to manage organizations. ### organization fields The following fields must be managed in this table: - `id` - `instance_id` - `name` - `state` enum (active, inactive) - `created_at` - `updated_at` - `deleted_at` DISCUSS: should we add a `primary_domain` to this table so that we do not have to join on domains to return a simple org? We must ensure the unique constraints for this table matches the current commands. ### organization repository The repository must provide the following functions: Manipulations: - create - `instance_id` - `name` - update - `name` - delete Queries: - get returns single organization matching the criteria and pagination, should return error if multiple were found - list returns list of organizations matching the criteria, pagination Criteria are the following: - by id - by name pagination: - by created_at - by updated_at - by name ### organization events The following events must be applied on the table using a projection (`internal/query/projection`) - `org.added` results in create - `org.changed` sets the `name` field - `org.deactivated` sets the `state` field - `org.reactivated` sets the `state` field - `org.removed` sets the `deleted_at` field - if answer is yes to discussion: `org.domain.primary.set` sets the `primary_domain` field - `instance.removed` sets the the `deleted_at` field if not already set ### acceptance criteria - [x] migration is implemented and gets executed - [x] domain interfaces are implemented and documented for service layer - [x] repository is implemented and implements domain interface - [x] testing - [x] the repository methods - [x] events get reduced correctly - [x] unique constraints # Additional Context Replace this example with links to related issues, discussions, discord threads, or other sources with more context. Use the Closing #issue syntax for issues that are resolved with this PR. - Closes #https://github.com/zitadel/zitadel/issues/9936 --------- Co-authored-by: adlerhurst <27845747+adlerhurst@users.noreply.github.com>
68 lines
2.1 KiB
Go
68 lines
2.1 KiB
Go
package repository
|
|
|
|
import (
|
|
"context"
|
|
|
|
"github.com/zitadel/zitadel/backend/v3/domain"
|
|
"github.com/zitadel/zitadel/backend/v3/storage/database"
|
|
)
|
|
|
|
type userMachine struct {
|
|
*user
|
|
}
|
|
|
|
var _ domain.MachineRepository = (*userMachine)(nil)
|
|
|
|
// -------------------------------------------------------------
|
|
// repository
|
|
// -------------------------------------------------------------
|
|
|
|
// Update implements [domain.MachineRepository].
|
|
func (m userMachine) Update(ctx context.Context, condition database.Condition, changes ...database.Change) error {
|
|
builder := database.StatementBuilder{}
|
|
builder.WriteString("UPDATE user_machines SET ")
|
|
database.Changes(changes).Write(&builder)
|
|
writeCondition(&builder, condition)
|
|
m.writeReturning()
|
|
|
|
_, err := m.client.Exec(ctx, builder.String(), builder.Args()...)
|
|
return err
|
|
}
|
|
|
|
// -------------------------------------------------------------
|
|
// changes
|
|
// -------------------------------------------------------------
|
|
|
|
// SetDescription implements [domain.machineChanges].
|
|
func (m userMachine) SetDescription(description string) database.Change {
|
|
return database.NewChange(m.DescriptionColumn(), description)
|
|
}
|
|
|
|
// -------------------------------------------------------------
|
|
// conditions
|
|
// -------------------------------------------------------------
|
|
|
|
// DescriptionCondition implements [domain.machineConditions].
|
|
func (m userMachine) DescriptionCondition(op database.TextOperation, description string) database.Condition {
|
|
return database.NewTextCondition(m.DescriptionColumn(), op, description)
|
|
}
|
|
|
|
// -------------------------------------------------------------
|
|
// columns
|
|
// -------------------------------------------------------------
|
|
|
|
// DescriptionColumn implements [domain.machineColumns].
|
|
func (m userMachine) DescriptionColumn() database.Column {
|
|
return database.NewColumn("description")
|
|
}
|
|
|
|
func (m userMachine) columns() database.Columns {
|
|
return append(m.user.columns(), m.DescriptionColumn())
|
|
}
|
|
|
|
func (m *userMachine) writeReturning() {
|
|
builder := database.StatementBuilder{}
|
|
builder.WriteString(" RETURNING ")
|
|
m.columns().Write(&builder)
|
|
}
|