9 docs tagged with "permissions"

Multiple blueprints can be composed into one master blueprint which specifies the deployment model for multiple included blueprints, by using includeBefore and includeAfter parameters. This allows you to scale your deployment and release models with any number of blueprints. During the implementation of a composed blueprint, the CLI will work through the blueprints in the sequence defined, merging the questions into a single list and applying any custom values that were defined in the composed blueprint. For more information on the YAML fields that enable composable blueprints, see IncludeBefore/IncludeAfter fields for composability.

This topic covers the configuration options available for customizing how Deploy handles large artifact deployments, including the in-memory processing threshold, executable detection regex, and JVM heap sizing guidance.

Deploy 26.1 and later supports deploying artifacts larger than 2 GB. Large artifacts are transferred using a streaming approach instead of being fully loaded into memory, which significantly reduces memory pressure during deployment. This topic covers which artifact types are supported, how permissions are handled, storage compatibility, and best practices.

This topic explains how Deploy processes archive formats internally, why the 2 GB boundary exists for ZIP archives, how adaptive permissions work when POSIX metadata is unavailable, and which storage backends support large artifacts.

You can specify and maintain global permissions, roles, and users for Deploy in YAML, enabling you to manage this aspect of your Deploy configuration "as code".

This topic describes the Permission service in Digital.ai Deploy.

This topic explains the roles and permissions in Deploy.

This topic provides Deploy provides information about fine-grained security settings based on roles and permissions that you can configure in the GUI and through the command-line interface (CLI).

This topic describes the default permission settings in Deploy after installation. Initially, no permissions are granted to any user, except for administrator users, who have all permissions.