-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
force:auth:sfdxurl command stopped working in January 14 release #801
Comments
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. |
@daveespo isn't the command Granted, if you used to do |
Is the alias broken in the recent update? I cant no longer use sfdx force:auth:jwt:grant, however sfdx auth:jwt:grant works. |
@amphro -- my bad .. yes, it's
|
Perhaps it's really the tarball that's messed up. If I unpack the tarball and This is what's installed after the installer finishes:
But if I This is what gets installed after
|
@daveespo the most recent release of the CLI has moved force:auth commands to the auth namespace ... i.e. drop the force: https://github.com/forcedotcom/cli/blob/main/releasenotes/README.md#50133-january-14-2021---cli-7842 |
It's not that we don't have a workaround, it's that we have tooling and scripts and some are not as easily changed as others. This change was supposed to be phased in as the Release Notes indicate. |
I am facing similar issue with user namespace not available as well. |
Using just auth instead of force:auth seems to solve that problem, but then I get a different error |
We are also facing similar issue, sfdx force:auth:jwt:grant › Warning: force:auth:jwt:grant is not a sfdx command. It seems salesforce expects the command to be sfdx auth:jwt grant instead of sfdx force:auth:jwt grant. |
This issue has been linked to a new work item: W-8731764 |
The |
Summary
Our CI system pulls the latest tarball of SFDX and installs it during each build. Starting today, the build is failing to authorize the DevHub org via the
force:auth:sfdxurl
commandI have read the Release Notes for today's release and it explicitly says that the legacy commands should continue to work.
Additionally, I have read #787 but that specifically calls out issues using NPM installs of SFDX. This issue is present in the tarball install (https://developer.salesforce.com/media/salesforce-cli/sfdx-linux-amd64.tar.xz)
Steps To Reproduce:
sfdx update
)sfdx force:auth:sfdx:url
Expected result
I should be able to store an auth URL for an existing org in my SFDX client
Actual result
SFDX CLI Version(to find the version of the CLI engine run sfdx --version):
Windows 10 Pro and Ubuntu 18
The text was updated successfully, but these errors were encountered: