KoolReport's Forum

Official Support Area, Q&As, Discussions, Suggestions and Bug reports.
Forum's Guidelines

Alternative / automation of requiring auth.json token #1114

Closed APP opened this topic on on Oct 8, 2019 - 2 comments

APP commented on Oct 8, 2019

The current method of getting a token cant be integrated in our CI workflow because our developers have to manually login to get a auth key which is very annoying There must be a way to acquire a key using a cli/api call?

KoolReport commented on Oct 8, 2019

I understand however we do not release very often, just every quarter. A solution is to install KoolReport in separated folder and consider our library as your code so KoolReport does not need to be install everytime you run workflow.

KoolReport commented on Feb 7, 2020

Just want to follow up on this issue, it should not be problem with CI/CD anymore as the token's expiry now is following the expiry of subscription. Also if you own the Perpetual Usage or Perpetual Usage, Support & Upgrade the token will not be expired.

Build Your Excellent Data Report

Let KoolReport help you to make great reports. It's free & open-source released under MIT license.

Download KoolReport View demo
solved

None