[[appendix_helix_sync]] === Appendix B: Helix Sync Extensions WARNING: The following proposal is subject to change. The Helix Sync rules and workflow were never very well defined. ==== Project Extension JSON for Helix Sync The extension ID is `helixSync`. The content type for helix sync extension is `application/vnd.perforce.project.helixSync.v1+json`. ===== Helix Sync Properties [cols="2*", options="header"] |=== | Property | Description | `p4` | The p4 URL connection string to the Helix Versioning Engine instance. For example, `p4://P4USER=jdoe@perforce.mycompany.com:1666/` | `members` | List of user IDs that indicate that the user has flagged this project as one of "My Projects". Note: this is likely an artifact of a completely invalid workflow. |=== ==== Helix Sync Service Rules Projects with a Helix Sync extension will block projects with more than one branch. If no branch exists on create, a simple stream will be created in a //projects stream depot, and associated with the project.
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#2 | 15098 | tjuricek |
Revised project services to GET-only forms. With Helix Sync revising to integrate purely with Helix Cloud, this is the only thing we can reasonably define. |
||
#1 | 15090 | tjuricek |
Update _proposed_ API for project services. This is *very likely* to change, and will not be implemented until reviewed. |