=== Helix Versioning Engine Commands [[get_helix_versioning_engine_vX_commands_command]] ==== `GET /helix_versioning_engine/v[api]/commands/[command]` Execute a Perforce command that takes no input. This only allows commands that have been whitelisted on your system. See the <<system_configuration>> section for details. ===== Request URL Path Parameters [cols="3*", options="header"] |=== | Parameter | Required | Description | `api` | Yes | The Helix Versioning Engine API level. | `command` | Yes | The command name, that should be whitelisted in the system configuration. See <<system_configuration>>. |=== ===== Request Headers [cols="2*", options="header"] |=== | Header Name | Notes | `Authorization` | See <<authentication>> | `Accept` | `application/json` | `Content-Type` | `application/json` | `X-Perforce-Helix_Web_Services-*` | See <<per_request_configuration>> |=== ===== Response Headers [cols="2*", options="header"] |=== | Header Name | Notes | `Content-Type` | `application/json` |=== ===== Response Body JSON Responses are typically an array, mapped from the `p4 -ztag` output of a command. See <<error_responses>> for the format of failures. ===== Ruby Client See link:./helix_web_services_client_ruby/HelixWebServicesClient.html#command-instance_method[`HelixWebServicesClient#command`] [[post_helix_versioning_engine_vX_commands_command]] ==== `POST /helix_versioning_engine/v[api]/commands/[command]` Execute a Perforce command that accepts input, like a spec. This only allows commands that have been whitelisted on your system. See the <<system_configuration>> section for details. ===== Request URL Path Parameters [cols="3*", options="header"] |=== | Parameter | Required | Description | `api` | Yes | The Helix Versioning Engine API level. | `command` | Yes | The command name, that should be whitelisted in the system configuration. See <<system_configuration>>. |=== ===== Request Headers [cols="2*", options="header"] |=== | Header Name | Notes | `Authorization` | See <<authentication>> | `Accept` | `application/json` | `Content-Type` | `application/json` | `X-Perforce-Helix_Web_Services-*` | See <<per_request_configuration>> |=== ===== Request Body JSON The request body is a JSON structure, which becomes converted to a Ruby hash. This hash is used as input via the `p4.input` class property of P4Ruby. See link:http://www.perforce.com/perforce/doc.current/manuals/p4script/ruby.p4.html#ruby.p4.input.eq[`P4.input`] for more information. ===== Response Headers [cols="2*", options="header"] |=== | Header Name | Notes | `Content-Type` | `application/json` |=== ===== Response Body JSON See <<error_responses>> for the format of failures. ===== Ruby Client See link:./helix_web_services_client_ruby/HelixWebServicesClient.html#command_with_input-instance_method[`HelixWebServicesClient#command_with_input`]
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#1 | 15741 | ptomiak | Branch HWS for my use. | ||
//guest/perforce_software/helix-web-services/main/source/doc/helix_versioning_engine/commands.asc | |||||
#1 | 15622 | tjuricek |
Move source code to 'source/' subdirectory of branch. build/ will remain where it is. |
||
//guest/perforce_software/helix-web-services/main/doc/helix_versioning_engine/commands.asc | |||||
#3 | 15240 | tjuricek |
Set api level via request path on all Helix Versioning Engine methods. This will allow migration of applications to different P4D versions. Our internal methods (like project API) should attempt to handle backward compatibility similarly. P4WEBAPI-118 |
||
#2 | 15208 | tjuricek |
Revise 'command' implementation, tests, and documentaiton. This includes a change from a command blacklist to a whitelist. See P4WEBAPI-21 |
||
#1 | 15144 | tjuricek |
Setup stream spec tests and documentation. Also revised the documentation folder http_p4_web_api -> helix_versioning_engine |
||
//guest/perforce_software/helix-web-services/main/doc/http_p4_web_api/commands.asc | |||||
#1 | 13555 | tjuricek |
Starting Asciidoc conversion of documentation. Removed the "Shared Quality" document, that basically is online now at: https://confluence.perforce.com:8443/display/PWS/Quality+Assurance Adding some topology graphviz images used for online documentation. |