JetBrains CodeCanvas 2024.1 Help

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.

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.

Namespaces and user access

  • By default, only system administrators can create namespaces.

  • After a namespace is created, the system administrator assigns the Namespace Administrator role to a user, who then manages the namespace resources and settings.

  • A namespace is an entity that, in the first place, serves for the ease of resource administration. That is why, by default, namespaces are visible only to system administrators and the assigned namespace administrators.

  • Ordinary CodeCanvas users with the Member role don't see namespaces in the UI and have only indirect access to namespace resources:

    • Dev environment templates

      To create a dev environment based on a template, a user must be explicitly granted access to the template. Otherwise, they won't be able to see it in the list of available templates in CodeCanvas and in JetBrains Gateway.

    • Connections to Git repositories

      To work with a repository, a user must be explicitly granted permission to access it. Otherwise, they won't be able to create a dev environment based on the repository, even if they have access to the corresponding dev environment template.

    • Other template resources

      Ordinary users can't see or access other resources like warm-up parameters, connections to Docker registries, and others.

Last modified: 17 May 2024