There should be a way we can test ncm-ci against staging and maybe dev environments. Dev environments are a bit iffy, but may be do-able. I'm thinking env var.
We tried overriding the hard-coded prod url for ncm2-api in the script, which works for the first graphQL request, but the analyze-tree thingee seemed to be hardcoded to use prod.
The graphql package supports process.env.NCMAPI_URL for overriding the default api path, which is the only way ncm-analyze-tree connects to our apis. ncm-ci@6.1.0 no also supports this option.
There should be a way we can test
ncm-ci
against staging and maybe dev environments. Dev environments are a bit iffy, but may be do-able. I'm thinking env var.We tried overriding the hard-coded prod url for ncm2-api in the script, which works for the first graphQL request, but the analyze-tree thingee seemed to be hardcoded to use prod.