p4 extension

Manage the Helix Core Server extensibility mechanism.

Syntax

p4 extension --sample name

p4 extension --package dir

p4 extension --install file

p4 extension --delete [--yes] [--revision] [--path] name

p4 extension --configure extension [ --revision ] [ -o -i ]

p4 extension --configure extension [ --revision ] [ -o -i ] --name name

p4 extension --list --type type

Description

p4 extension manages the installation, versioning, and configuration of Helix Core Server Extensions. This command requires super access granted by p4 protect.

For server extensions, see p4 help serverextensionintro and p4 help serverextensiondev. See also Helix Core Extensions Developer Guide.

Options

--sample	Create a skeleton of a new Extension in a directory. Pass it the name of the Extension to be created.
--package	The --package flag creates a packaged Extension file from the named directory of files. The resulting file has the same name as the directory, but with the .p4-extension suffix.
--install	The full name of an Extension file on the client. The command installs it server-side. Packaged Extensions have the p4-extension file suffix.
--name	The name of the configuration to create or modify.
--revision	Which depot version of the Extension to configure. The default is the head revision. This option applies to the --configure option.
--list	Displays the installed extensions and their instances. If this option is specified with the --type=extensions, --list option, the output shows information about which extensions are installed, and --type=configs shows information about the different configurations.
--delete	Deletes an extension, its configurations, or both. To remove one specific revision and its instances, include the --revision option. To remove only the named instance config, include the --name option. To delete file-based instances by the part of the depot they affect, include the --path option. To remove all revisions of an extension and its configurations, omit the --name option.