Skip to content

Add support for custom WorkspaceTypes for newly created Organizations #16

@nexus49

Description

@nexus49

Context

  • In the future we need the ability to control which API's are enabled by default in a certain organization. What API's are enabled by default in a workspace in KCP is controlled by workspace types.
  • Today we have a static set of workspace types that are created from the installation operator.
  • In the future we need to create custom WorkspaceTypes for the Organization and then also for each child workspace of that Organization.

Task

  • Add a new workspacetype subroutine to the account operator that needs to be executed before the workspace creation.
  • This subroutine should create a new Workspacetype called <account-name>-org that will be used as a workspacetype for the to be created workspace.
  • This subroutine should also create a new Workspacetype called <account-name>-acc that will be used as defaultChildWorkspaceType within the <account-name>-org workspace type.
  • Experiment if we can use extend.with to have the new workspacetypes extend from the exist org/orgs to get their initializers but also to inherrit their defaultApibindings as a default. If defaultAPIBindings are not inherrited, then you'd need to copy the defaultAPIBindings from those workspaceTypes.
  • Test this setup in the local-setup first

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions