Wednesday, August 14, 2019

Change Log: 3.85.1654

Release 3.85.1654 is mostly focused on adding API enhancements that will allow me to do more administrative work without having to shell into the server.

Since the production version of the Manager is pretty much stabilized and I am not doing feature work anymore, there's almost nothing user-facing in this one except some low-key break/fix stuff (that most people probably didn't even notice was broken in the first place).

In fact, the most significant user-facing aspect of this release is that it continues the deprecation of, which will go away officially in January 2020: the old URLs now forward to URLs and, as I mentioned on the Manager's Twitter:

Since it is officially deprecated as of today, I'm not going to print the email address here, but the tweet basically confirms that the old support email at is officially shut down and will bounce.

Finally, as everyone knows by now, the indefinite delay of Waves three and four will continue for at least another year, but I still have plans for new KD software in 2019.

With any luck, I will be able to announce some specifics of those plans very soon! Could even be the first week of September 2019.

Watch this space for updates and, as usual, hit the jump for complete release notes.

Fixes and corrections

  1. Fixed a missing string substitution in app.models.__init__ that made user-facing asset-retrieval errors hard to decipher.
  2. Fixed the API admin panel to pull the correct GitHub stats.
  3. Cleaned up the text on the Dashboard about subscriptions.
  4. Added a new "Players" heading to the Help section of the legacy webapp and wrote a little blurb about adding players (which collected a few bits of a few different sections).
  5. forwards to now (includes www and api second-level domains).
  6. Removed an accidental > from the API error modal in the legacy app that created the appearance of a single period floating in space above the message (in Chrome; it straight-up broke the modal everywhere else).

Application Enhancements

  1. Updated some calls in to use the API key.
  2. The postJSONtoAPI() method in kdmManager.js now uses the API key as well.
  3. kdmManager.js error modals (the pink ones) now print a message when the API response is null (which mostly happens with a preflight/CORS/SSL error).
  4. Cleaned up the help-tips on the Survivor Sheet re: survivor 'tags' and 'notes' (the name is going to fully change from 'epithets' to 'tags' in the next version of the Manager and the API shortly).

API Development

  1. Removed some vestigial control elements from the admin panel, e.g. the logs, world daemon stats, etc.
  2. Cleaned up some of the flexbox issues (such as mandatory heights) causing messy presentation in the admin panel. The panel now uses 'Silverado' and 'Ruda' fonts (gotta stay on-brand).
  3. The API's default 'meta' block no longer includes information about the application admins.
  4. User subscription levels can now be set via the Admin panel.
  5. The API's default 'meta' block now includes a dictionary called 'subscriptions' that shows supported subscription levels.
  6. Created a new admin panel control interface for working with users:
    1. added the HTML
    2. created a new JS controller in adminPanel.js
    3. moved the user stats block from the general API admin panel to the user admin controls
    4. created a new route for retrieving user data via API call
  7. Did some other cleanup on the admin panel:
    1. the HR's in the main control raft go away after the admin user's JWT is set
  8. The settings.Settings object has a logger now.
  9. settings.get() pops off a debug warning about how the 'private' kwarg is deprecated.
  10. The subscriber section of user info now includes the 'level_handle', which is basically just 'level_' + the level; this facilitates look-ups in the panel and AKDM Manager. 
  11. List and dict type world values are not shown in the Admin panel's 'world stats' view.
  12. Started building out support API keys:
    1. The request now has a flag to indicate whether the API key on the request is valid
    2. The API now writes a warning to the logs when incoming requests for 'private' end points have no API key.
    3. API keys in the api_keys.cfg file (in the app root) are now loaded into the API when the server starts.
    4. API request response logs now track the name of the app associated with an API request.
  13. Unified the settings files in the object, so that all sections from both settings.cfg and settings_private.cfg are available in the settings object.
  14. The CLI now has the ability to dump API request response time log entries (for research/debug purposes).
  15. Addressed an issue where a JWT could sometimes fail to refresh an expired token from the legacy app due to weird headers.

No comments:

Post a Comment