Add support for Cloudflare API Token replacing legacy API Key #429
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
As stated here: https://developers.cloudflare.com/fundamentals/api/get-started/keys/
This small pull request will add support for users to use Cloudflare API tokens instead of email+API Key (which could also solve the problem stated here #302 ) that is more secured settings than entering the global API key.
As a result, only API token is needed, users won't need to set their Cloudflare email.
set the config
renew SSL