Environment variables not being read when bootsraping the config for the CLI

paularah commented 2 years ago

This is kinda related to #113 except in this case for the CLI component. Not sure if I am correct, but the CLI component doesn't rely on DC to receive its env variables so the response to #113 isn't applicable here.

Actual Behavior:

The environment variable to pick the right config file doesn't load up.

Error: ENOENT: no such file or directory, open '/xxxx/purple-team/purpleteam/config/config.undefined.json'

...

Expected Behavior:

NODE_ENV should be cloud, local or localtest

...

Steps to Reproduce:

official docs step for setting up the CLI

...

Environment:

Specific purpleteam project and version? latest
Running locally or in the cloud? locally
Details of your specific System Under Test (SUT)? NodeGaot
Which purpleteam components are running on which Operating System and version? everything except CLI
Anything else that will set the stage for us understanding your context? N/A

Additional Details:

(e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, Github Discussions, links for us to have context, eg. code from your repository, a discussion in stackoverflow, gitter, etc)

Checklist

[x] I have read the documentation.

binarymist commented 2 years ago

The environment variable to pick the right config file doesn't load up.

This is a manual step as detailed. Did you do this step? How exactly are you setting NODE_ENV?

paularah commented 2 years ago

My bad, Missed the step for exporting the env variable. Thanks. I'm closing this

purpleteam-labs / purpleteam