# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#7 | 19535 | drobins | Refactor package names to hws | ||
#6 | 19399 | tjuricek |
Upgrade to spark 2.5 which requires a different path for the version information. Spark 2.5's static file matching seems to conflict with just using the "/api" path since a "/publicsite/api" directory actually exists. You end up with a 500 error (NPE exception) if you attempt to map that path. Also, disable the failing RPM test for now. |
||
#5 | 19098 | tjuricek |
JavaScript Client SDK labels spec CRUD tests. Identified another parameter naming conflict, which only pops up in the javaScript client because I didn't choose to automatically rename parameters for people. (I don't think it's a good idea to just say "label0", "label1", etc., especially when they're different types.) |
||
#4 | 19012 | tjuricek | Revised Java client SDK, added ApiClient reference, restructured documentation. | ||
#3 | 19002 | tjuricek |
Improve API to interact with multiple p4ds. The configuration now requires an explicit setting of what P4Ds HWS can talk to via the 'P4D config dir', where there's a file indicating connection settings per p4d, and importantly, an ID. This is the "server ID" referenced everywhere. Most methods now require a server ID to indicate which p4d to manipulate. In the future, it's likely we will interact with *multiple* p4d instances on some services. This completely removes the ability to run HWS as a kind of an "open proxy" to whatever p4d you want. Given the nature of the change and the lack of priority, we've removed Helix Cloud testing and disabled several methods from their "Helix Cloud" implementation. These will be relatively easy to bring back, we'll just need a new method from Raymond that lists the "allowed server IDs" that map to the HWS configured server IDs for a particular user. Another notable aspect of this change is the use of JSON Web Token to create our authentication key. We associate this key with an in-memory "session" that contains the P4D tickets we use to authenticate users. The JWT token, by default, is assigned a timeout, which allows HWS to block further access to underlying servers without having to interact with multiple auth backends. If any backend fails with that session, the user will get a 403. If you disable the timeout, you'll need to ensure your clients clear out sessions. |
||
#2 | 18798 | tjuricek |
Report supported platform versions in the default request, if we accept application/json. Added a method to the Java client SDK to check if it's a supported version. |
||
#1 | 18795 | tjuricek | Use point-release versioning for the client SDKs and installers. | ||
//guest/perforce_software/helix-web-services/main/source/clients/2016.1/java/src/main/java/com/perforce/helix_web_services_client/ApiClient.java | |||||
#5 | 18788 | tjuricek | Correct references to URL paths in asciidoc and add minor release number to default version string. | ||
#4 | 18786 | tjuricek | Prefix all paths with /api, and remove <, > characters in documentation which breaks javaDoc at the moment. | ||
#3 | 18737 | tjuricek | Ensure that checking if the system is OK does just returns false if the server isn't running, instead of throwing an exception. | ||
#2 | 18727 | tjuricek | Convert the status method to be part of the documented API, and convert the login-related models. | ||
#1 | 18679 | tjuricek |
Revising HWS paths to work primarily at product version 2016.1. The swagger definitions will primarily work at a major platform release number. We will generate new clients for each major release, and ensure backwards compatibility as time goes on by keeping the older clients around in the tree. Note: These are JUST URLs, and do not include other revisions we plan on making shortly. |
||
//guest/perforce_software/helix-web-services/main/source/clients/java/src/main/java/com/perforce/helix_web_services_client/ApiClient.java | |||||
#5 | 18605 | tjuricek |
Document a simplified method for obtaining the Java client SDK handle. The client SDK is included as a part of the distribution. Javadoc is included in a subdirectory and hosted directly. A stupid simple HTML page was added by default to give people something to access right after installation. |
||
#4 | 18585 | tjuricek | Adding JavaDoc reference for client libraries to package distributions. | ||
#3 | 18524 | tjuricek |
Add a "trust everything" mode to the generated Java client for testing our installed packages. Also, check in the client's dependencies as well via our "vendor" declarations. It's unclear how we'll distribute the client SDK code, probably as a group of jar files. We'll see. |
||
#2 | 18515 | tjuricek |
Replacing java_client with Swagger-based clients/java project. - Switched implementations of the Swagger client to use okhttp with gson. - Added the version to the "status" method, and hey, added that method to the spec - Added templates to the java code generator to add some default methods, fixing some import issues in Gradle NOTE: We may want to break down the API a bit and restructure it. |
||
#1 | 18488 | tjuricek |
Swagger Java client (initial version). This contains a basic configuration for the java client, which mostly decides package location, etc. Notably, the license must be ASL under the SmartBear copyright. |