Change | User | Description | Committed |
---|---|---|---|
19575 | swellard | Refactor REST paths First round * Remove use of hardcoded repeated strings * Fix checkst...yle issues « |
9 years ago |
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. « |
9 years ago |
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. « |
9 years ago |
18035 | tjuricek | Preliminary distribution formats with first-pass post-install configuration script for Lin...ux only. This is *manually verified* at the moment. The testing framework is TBD. This contains *preliminary* hooks for .deb and .rpm packages. Those are *completely untested* and not configured. « |
9 years ago |
18025 | tjuricek | Converted logging framework to use log4j 2. This will default the current level to "eve...rything" if no configuration file is specified (which is typically what we want since that's almost always used for debugging). « |
9 years ago |
17351 | tjuricek | Allow system properties to adjust config, and use log4j as the logging system by default (...from Simple). We may switch to log4j 2, I am still ironing out deployment. « |
9 years ago |
17220 | tjuricek | Basic web hooks for custom project implementations. Also, a simple web service app to d...o some basic manual testing. « |
9 years ago |
17140 | tjuricek | Integrating porting work from development branch. This work is now ready for testing/CD... integration. « |
9 years ago |