mirror of
https://github.com/zitadel/zitadel.git
synced 2025-07-15 21:38:36 +00:00
7eb45c6cfd
# Which Problems Are Solved Resource management of projects and sub-resources was before limited by the context provided by the management API, which would mean you could only manage resources belonging to a specific organization. # How the Problems Are Solved With the addition of a resource-based API, it is now possible to manage projects and sub-resources on the basis of the resources themselves, which means that as long as you have the permission for the resource, you can create, read, update and delete it. - CreateProject to create a project under an organization - UpdateProject to update an existing project - DeleteProject to delete an existing project - DeactivateProject and ActivateProject to change the status of a project - GetProject to query for a specific project with an identifier - ListProject to query for projects and granted projects - CreateProjectGrant to create a project grant with project and granted organization - UpdateProjectGrant to update the roles of a project grant - DeactivateProjectGrant and ActivateProjectGrant to change the status of a project grant - DeleteProjectGrant to delete an existing project grant - ListProjectGrants to query for project grants - AddProjectRole to add a role to an existing project - UpdateProjectRole to change texts of an existing role - RemoveProjectRole to remove an existing role - ListProjectRoles to query for project roles # Additional Changes - Changes to ListProjects, which now contains granted projects as well - Changes to messages as defined in the [API_DESIGN](https://github.com/zitadel/zitadel/blob/main/API_DESIGN.md) - Permission checks for project functionality on query and command side - Added testing to unit tests on command side - Change update endpoints to no error returns if nothing changes in the resource - Changed all integration test utility to the new service - ListProjects now also correctly lists `granted projects` - Permission checks for project grant and project role functionality on query and command side - Change existing pre checks so that they also work resource specific without resourceowner - Added the resourceowner to the grant and role if no resourceowner is provided - Corrected import tests with project grants and roles - Added testing to unit tests on command side - Change update endpoints to no error returns if nothing changes in the resource - Changed all integration test utility to the new service - Corrected some naming in the proto files to adhere to the API_DESIGN # Additional Context Closes #9177 --------- Co-authored-by: Livio Spring <livio.a@gmail.com>
48 lines
886 B
Go
48 lines
886 B
Go
package domain
|
|
|
|
import (
|
|
"github.com/zitadel/zitadel/internal/eventstore/v1/models"
|
|
)
|
|
|
|
type ProjectRole struct {
|
|
models.ObjectRoot
|
|
|
|
Key string
|
|
DisplayName string
|
|
Group string
|
|
}
|
|
|
|
type ProjectRoleState int32
|
|
|
|
const (
|
|
ProjectRoleStateUnspecified ProjectRoleState = iota
|
|
ProjectRoleStateActive
|
|
ProjectRoleStateRemoved
|
|
)
|
|
|
|
func (s ProjectRoleState) Exists() bool {
|
|
return s != ProjectRoleStateUnspecified && s != ProjectRoleStateRemoved
|
|
}
|
|
|
|
func (p *ProjectRole) IsValid() bool {
|
|
return p.AggregateID != "" && p.Key != ""
|
|
}
|
|
|
|
func HasInvalidRoles(validRoles, roles []string) bool {
|
|
for _, roleKey := range roles {
|
|
if !containsRoleKey(roleKey, validRoles) {
|
|
return true
|
|
}
|
|
}
|
|
return false
|
|
}
|
|
|
|
func containsRoleKey(roleKey string, validRoles []string) bool {
|
|
for _, validRole := range validRoles {
|
|
if roleKey == validRole {
|
|
return true
|
|
}
|
|
}
|
|
return false
|
|
}
|