Support dotenv based dynamic environments in API Fuzzing

Problem

GitLab supports using dotenv files to define a dynamic environment (url, name, etc.). API Fuzzing should support this use case.

Proposal

Investigation needed to determine how to support.

  1. How do we know which .env file is being used?
  2. How do we know which variable is the url?
  3. Does GitLab CI Runner expose the environment url somehow?
    1. Initial test showed $CI_ENVIRONMNET_URL is not set after environment configured using environment: $URL
  4. User could provide the dotenv file & variable to use. Would be nice to have it automatic.

Links

/cc @sethgitlab @stkerr

Edited by Michael Eddington