For the longest time, I have started a VS Code project and added a destructiveChanges.xml manifest (left the original package.xml empty) and then would run a command in terminal to deploy by manifest.
I forget the exact SFDX command I was using that would work. I would typically just arrow through my command history to find the last time I used it... but now I have a new machine and am history-less.
That's ok! I want to adopt the new SF commands anyhow. So I tried this:
sf project deploy start -o PRD --manifest manifest/destructiveChanges.xml --test-level RunLocalTests
which nets me a "No source-backed components present in package" error
For fun I tried just setting manifest to the folder where they both are like so:
sf project deploy start -o PRD --manifest manifest --test-level RunLocalTests
and that got "manifest exists but is not a file"
My XML files are proper because I can zip them up and deploy them through workbench.
What am I doing wrong? What would be the correct SF command to deploy?
Hey @Michael Farrington,
If you check that link project Commands | Salesforce CLI Command Reference | Salesforce Developers you will see that (under project deploy start) you are able to define the destructive changes with --pre-destructive-changes or --post-destructive-changes.
