-
-
Notifications
You must be signed in to change notification settings - Fork 116
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
Error due to SFDX deprecation #904
Comments
Hi @bmehtawebsummit! Thanks for raising this issue and thanks for contributing in making this project better! I can see warnings but no errors. Could you provide more information please ? |
HI @scolladon , Thanks for giving reference of the issue. So what I understood is the warning can be ignored ? for the warning below
I am not using apiVersion config name in my entire script anywhere, I have double checked SGD command, putting below for your reference.
If the warning can be ignored then I have a real issue that after sfdx sgd:source:delta command a package xml is generated but sfdx force:source:deploy -x ${PACKAGE_XML_PATH} -w 30 -u ${SF_USERNAME} command right after that is deploying more than specific in the package/package.xml. So I was wondering if this has something to do with the warning I am seeing. This mainly happens when I am trying to create/update a field. It tried to deploy the entire object where previously it use to deploy just a field. |
Hum... I think the plugin may have added the SObject in the package.xml, this is why then it could try to deploy the full object. Could you show the diff ( |
HI @scolladon Sorry for the delay. For eg : I made a description adjustment on a field Cost__c on account object the output of Package XML is Account.Cost__c CustomField 58.0It is still attempting to deploy the entire object |
That is weird... Based on those new information I would say the plugin as done its job correctly. The package.xml generated is expected. What is concerning is the deploy command is deploying the whole object when asking to only deploy a field. What is the command used to deploy ? |
sfdx force:source:deploy -x package/package.xml -w 30 -u ************************** -c -l RunSpecifiedTests -r NoTestRun |
I think this bug is located on the sfdx cli itself then... If you agree I'll close this one |
Hi @scolladon I am raising ticket with salesforce cli but I wanted to confirm if my understanding is correct that SGD is still working on SFDX command? sfdx commands have been deprecated and will be removed on Nov 2024 as per this link forcedotcom/cli#2974 Please advise what is your plan on migration and what would you advise to me that should I check for SFDX or try changing to sf command ? |
Hi @bmehtawebsummit, We are migrating soon to the new plugin v2 architecture. I think you should migrate to sf command 👍 |
I tried and getting following error › Warning: sgd source delta is not a sf command. |
Have you tried |
yes, I tried that too. |
I tried this command and that also did not work |
What you can do is:
We are currently working on migrating to the plugin v2 architecture. |
Hi, I have written following in my docker file : RUN npm install @salesforce/cli --global Please let me know what should I change here? |
Nothing to change here When you install @salesforce/cli you have both |
thanks for your help |
Issue verification check:
What is the problem?
What is the parameter and the value you used with it?
What is the expected result?
What is the actual result?
Steps to reproduce
Execution context
Operating System: … Docker
yarn version: …
node version: …v20.17.0
git version: …git version 2.45.2
sfdx version: …sfdx-cli/47.15.1 linux-x64 node-v20.17.0
sgd plugin version: … should be the latest
More information (optional)
The text was updated successfully, but these errors were encountered: