-
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
Deployment Problems #942
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. |
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. |
yes, it works. |
If you have a deployment (
source:deploy
,mdapi:deploy
,source:push
) that's behaving badly, you may be experiencing a bug related to a recent change in how the metadata API is used.Starting in version 51.0, Salesforce CLI uses REST by default for deployments. Previously it used SOAP by default. Unfortunately, there's some problems with the REST API version.
How to change it back to use SOAP Metadata API:
mdapi:deploy
there is a--soapdeploy
flag you can addsfdx config:set restDeploy=false --global
to change it everywhere, or without--global
to change it at the project levelSFDX_REST_DEPLOY=false
in the environmentmore information on environment and configuration here: https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_dev_cli_config_values.htm
UPDATE: The REST by default change has been rolled back in version 51.7 released on April 8th. You can find more information in this Trailblazer Community post and in the CLI Release notes for 51.7.
The text was updated successfully, but these errors were encountered: