Blast Radius , when launched in --serve mode, does some pretty weak error reporting, and does nothing to help users resolve problems. It asks the user to look into several possible issues, rather than checking itself...
To observe the current (undesired) behavior, run Blast Radius in an empty directory:
[...]$ mkdir tmp
[...]$ cd tmp
[...]$ blast-radius --serve
A short list of tests/checks to automate:
Check if graphviz is installed (is dot in its path?)
Check if terraform is installed (is terraform in its path?)
Is the current project initialized?
maybe it is, but a module is missing and terraform get needs to run...
maybe it is, but it's initialized for the run arch/os...
For that matter, does this directory contain files ending in .tf or .tfvars?
Blast Radius , when launched in
--servemode, does some pretty weak error reporting, and does nothing to help users resolve problems. It asks the user to look into several possible issues, rather than checking itself...To observe the current (undesired) behavior, run Blast Radius in an empty directory:
A short list of tests/checks to automate:
dotin its path?)terraformin its path?)terraform getneeds to run....tfor.tfvars?The error page could link to relevant documentation, including the Blast Radius online documentation at https://28mm.github.io/blast-radius-docs