P4 Cloud blocked and restricted commands
If your team subscribes to P4 Cloud, Perforce manages your P4 Server. As a P4 Cloud user, your administrative permissions are limited, and some commands are blocked or restricted.
See also P4 Cloud configurables.
To learn more about P4 Cloud, see the P4 Cloud Documentation.
Blocked commands
P4 Cloud users receive an error message if they attempt to run a blocked command. If you think it is necessary to run a blocked command, contact a P4 Cloud administrator.
p4 commands that start with: |
Blocked commands |
---|---|
a |
|
b |
|
c |
|
d |
p4 dbschema, p4 dbstat, p4 dbverify, p4 delete (graph), p4 describe (graph), p4 diagnostics, p4 diff (graph), p4 diff2 (graph), p4 dirs (graph) |
e |
|
f |
p4 failback, p4 failover, p4 fetch, p4 filelog (graph), p4 files (graph), p4 fstat (graph) |
h |
|
j |
|
l |
p4 ldap, p4 ldaps, p4 ldapsync, p4 lock (graph), p4 logappend, p4 logexport, p4 logparse, p4 logrotate, p4 logschema, p4 logtail |
m |
|
o |
|
p |
p4 ping, p4 print (graph), p4 proxy, p4 prune, p4 pull, p4 push |
r |
p4 reconcile (graph), p4 reload, p4 remote, p4 remotes, p4 replicate, p4 resolve (graph), p4 restore, p4 resubmit, p4 revert (graph) |
s |
p4 server, p4 serverid, p4 storage, p4 submit (graph), p4 switch (graph), p4 sync (graph) |
t |
|
u |
p4 unload, p4 unlock (graph), p4 unsubmit, p4 unzip, p4 upgrades |
v |
Restricted commands
P4 Cloud users receive an error message if they attempt to run a restricted command with an argument that is not allowed. For example, p4 configure history
returns The command "configure history" is not allowed in P4 Cloud.
In the following, "reserved prefix" refers to the perforce
and svc_
prefixes.
Command |
Restriction |
---|---|
The following are allowed: |
|
p4 branch | An Owner field cannot specify an entity whose name includes a reserved prefix.
|
An Client workspaces cannot be created, modified, or deleted if their name starts with a reserved prefix. A |
|
For the configurables listed at P4 Cloud configurables, the following are allowed: |
|
These counters cannot be modified: Counters cannot be created, modified, or deleted if their names start with a reserved prefix. |
|
p4 dbstat | Only the -s option is allowed. |
Depots cannot be created, modified, or deleted if their names start with a reserved prefix. A An |
|
p4 extension | Only the --list option is allowed. |
Groups cannot be created, modified, or deleted if their names start with a reserved prefix. An A A |
|
Key/value pairs cannot be created, modified, or deleted if the key names start with a reserved prefix. |
|
p4 license | Only the -u option is allowed. |
p4 passwd | The passwords of users whose names start with a reserved prefix cannot be changed. |
p4 property | Properties cannot be created, modified, or deleted if their names start with a reserved prefix. |
The last three lines of the protections table cannot be changed. |
|
p4 renameclient | Client workspace names that start with a reserved prefix cannot be renamed. |
p4 renameuser | Users that start with a reserved prefix cannot be renamed. |
p4 server | Servers are read-only, so only the -o option is allowed with a server ID. |
Streams cannot be created, modified, or deleted if they belong to a depot with a reserved prefix. An |
|
p4 triggers | Triggers are read-only, so only the -o option is allowed. |
p4 user | Users cannot be created, modified, or deleted if their names start with a reserved prefix. |