Namespaces
A namespace is an organizational entity that groups together related resources like Git repositories, secrets, dev environment templates, and other settings. For example, a namespace can represent a project your team is working on or a group of projects that share common resources. To start working with remote dev environments, you must first create and configure a namespace.
Namespace resources
A namespace groups together the following resources:
Dev environment templates that define the resources and settings for project dev environments: an instance type, a container image, environment variables, etc.
Connections to Git repositories that store project code.
Warm-up parameters – parameters (including sensitive data like access credentials or tokens) that are required to prepare data (project indexes, dependencies, etc.) for a warm-up snapshot. Warm-up snapshots are used to speed up dev environment start-up.
Connections to Docker registries that store container images used in dev environments.
Who creates namespaces
There are two main policies for creating namespaces in CodeCanvas:
Default (system admin creates namespaces)
By default, only system administrators can create namespaces.
It is a responsibility of a system administrator to create namespaces for the organization's projects. After the administrator creates a namespace and assigns namespace administrators, they can start configuring the namespace.
Self-service (users create namespaces)
Alternatively to the default policy, the system administrator can allow other users in the organization to create namespaces. A system administrator can:
Create a custom role and grant it the Create namespaces permission. Assign this role to specific users or groups.
Grant the Create namespaces permission to the Member role. In this case, all CodeCanvas users will be able to create namespaces.