a3020 / centry Goto Github PK

When domain subscriptions are updated to Centry Portal, we send along the API token. With the API token, the portal can then retrieve information from the Centry Add-on.

It'd be nice to have a setting that would enable / disable regeneration of the API token, each time an instance updates its subscription in the portal.

Because this could affect other API 'consumers', we should make this a setting.

I prefer to have it disabled at first, and make it enabled once it seems stable.

It'd be handy to have access to the absolute path of a C5 installation.

E.g. to:

• Export a list of C5 installations and their absolute path
• Create a list of paths to call the run-schedule CLI command

In the portal one can select a bunch of domains and say for example 'ok, run these 5 jobs each day'. If done so, during domain synchronization the schedule is being sent to Centry Add-on. A queue checker that runs on the server should then execute the stored schedules / jobs.

Requirements:

• Centry Add-on should store schedules in the database. Multiple schedules should be possible. Each schedule should have a cron expession and an array of job handles.
• A custom command should handle the schedules via CLI.

It would nice if one or more IP addresses can be configured to allow access to the API in order to increase security.

If no IP address is defined then we can either:

1. Resolve the domain name of the endpoint (centry.nl in most of the cases), or
2. Allow all IP addresses