Allow nxCloudId to also be defined as an env var

[dmcweeney]

Hi I only want to use NX Cloud in pipelines however the nxCloudId must be specified in the nx.json.
When running commands locally this results in annoying 401 errors being displayed to the developers after executing commands.

NX Nx Cloud Problems

401: Unable to connect to Nx Cloud. (code: 401)

View logs and run details at https://nx.app/runs/hash

One can use env var NX_CLOUD_ACCESS_TOKEN in pipelines - it would be really useful to also allow nxCloudId be defined as an env var so that it can be completely separated nx.json.

Thanks, Donal

[StalkAltan]

@dmcweeney if you are specifying NX_CLOUD_ACCESS_TOKEN, you shouldn't need to have nxCloudId specified at all in nx.json. They are two different authentication methods.

Can I ask why you don't want to have Nx Cloud enabled locally? You can set permissions such that developers cannot write to the remote cache, and local usage does not contribute to your billing since you are not triggering CI Pipeline Executions. You would still benefit from cache entries created during your CI process.

With your current setup, the only thing required would be having your team authenticate via 'nx-cloud login'.

[dmcweeney]

Hi @StalkAltan,

if you are specifying NX_CLOUD_ACCESS_TOKEN, you shouldn't need to have nxCloudId specified at all in nx.json. They are two different authentication methods.

Super... I'll try that - that was not clear from the docs...

Can I ask why you don't want to have Nx Cloud enabled locally?

Small steps! The CI builds are the biggest time bottleneck at the moment. When we get those performing well with NX Cloud we can start hooking into the local dev envs.

Thanks, Donal