Open mcarvin8 opened 2 days ago
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.
Summary
This was previously reported in https://github.com/forcedotcom/cli/issues/2570 and closed due to version of NodeJS.
I'm recreating this issue as I've seen this warning upon multiple deployment pipelines with the latest Salesforce CLI and my node js version is node-v20.18.0. I've seen this warning with both CLI version 2.63.7 and 2.65.8. We recently made a major CLI upgrade (from 2.10.2 which didn't have this warning).
When running the
echo {url} | sf org login sfdx-url --set-default --alias {alias} --sfdx-url-stdin
command to authenticate to our org before starting a deployment in our CI/CD container, we consistently get this NodeJS warning.I'm just running the
echo {url} | sf org login sfdx-url --set-default --alias {alias} --sfdx-url-stdin
command directly in the CI/CD shell which uses the environment variables defined at the job-level for authentication.Authentication to the org is still successful and the deployment starts per normal, but I've consistently received this warning the 1st time I run the org login command in each new container. If I run a 2nd org login command in the same session, the warning doesn't appear, so it appears to be isolated to running the org login command the first time in a fresh container instance.
Steps To Reproduce
echo {url} | sf org login sfdx-url --set-default --alias {alias} --sfdx-url-stdin
command in a newly created Docker containerExpected result
authentication is successful without any Node warnings
Actual result
authentication is successful with the Node warning consistently in multiple containers when running the command the 1st time.
Warning doesn't happen when running org login command multiple times in the same session.
System Information
Ubuntu latest Docker GitLab CI/CD
Here's our
Dockerfile
. Open to any suggestions but this is a pretty straight forward container and we need to publish custom container images to our work's container registry to avoid hitting a Docker Hub pull rate limit.This
Dockerfile
is the same as we used with 2.10.2, except for the CLI version declared and the addition of the newSF_CI_HEARTBEAT_FREQUENCY_MS
environment variable.