.circleci/config.ymlin your repo, select the branch it's on to start building
panther_analysis_tool testto ensure your unit tests are passing.
panther_analysis_tool uploadto upload new detections to your Panther instance.
PANTHER_API_HOSTare required for these commands to execute successfully.
PANTHER_API_TOKENis the value of the API token you obtained in step 1.
PANTHER_API_HOSTis the API URL of your Panther Instance. For example, if your Panther domain is https://acme.runpanther.net, then your GraphQL API URL is
PANTHER_API_HOSTare passed into the job to allow for correct authentication. These can be stored encrypted as repository secrets. The process of adding repository secrets is covered in the next section.
panther-analysisrepository Click ... on the right side of the project then click Project Settings.
$INTERNAL_API_HOSTwithin the Project Settings in CircleCI for your forked version of
panther-analysisrepo in your organization. This will serve as your working copy of
panther-analysis, and any changes required by your organization can be made here and will undergo any configured CI checks that you define. Note that as mentioned in the previous section, a CircleCI config file is already present in this repository and can be used if desired; you will need to enable this new forked project in your instance of CircleCI.
panther-analysisin your GitHub org.
.github/workflows/fork-sync.ymland configure the action as desired.