Greetings All,
After several months of work, all existing EveKit endpoints are now ported to ESI on the beta site, which means it’s time to update the main site. This migration is scheduled to happen on 2018-04-14 starting at 1600 UTC. The update should take about 1 hour. During this time, synchronization will stop and access to model objects may or may not work. Access to the main site will continue to work for things like adding or removing accounts.
As noted in the first post in this thread, after the update you’ll need to add ESI credentials if you’d like your data to continue to be updated. If you do not add credentials, your synchronization accounts will be assigned a dummy ESI credential which will allow non-scoped endpoints to continue to update (namely: public character and corporation sheet endpoints). All other endpoints will cease updating until you add properly scoped ESI credentials.
Some users download their EveKit data into jEveAssets. Post update, those users will need to download a new version of jEveAssets designed to work with the updated EveKit models. Expect an announcement shortly from @Golden_Gnu on when the new release of jEveAssets will be available.
Porting from the XML API to the ESI required substantial changes to some EveKit models. I’ve made my best effort to preserve as much historical data as possible during the port. Nonetheless, a very small amount of historical data will be lost during the update. Important things like the wallet journal and transactions are definitely preserved. You can read about all of the model changes (and potential historic loss) in the porting notes here. Feel free to post if you have any questions or concerns.
During the porting process, a total of 55 separate XML APIs calls were updated to their ESI counterparts. Likewise, 68 separate EveKit models were updated to accommodate ESI changes. And of course all unit and integration tests were updated to verify the changes.
That was fun. Let’s never do this again.
cheers!
Sal