In part two of this series, learn how to migrate to the new Salesforce CLI sf (v2), now generally available for developers …
Here are highlights from article The Salesforce CLI sf (v2) Is Here! — Part 2
1. Introduction to sf (v2):
– Salesforce CLI (command line interface) is evolving with time.
– sf (v2) is the new and improved Salesforce CLI.
– Part 1 of the blog series discussed what’s new with sf (v2).
2. Introduction to sf -style commands:
– The ongoing work on the Salesforce CLI Unification has resulted in changes to commands.
– The CLI now includes two executables: sfdx and sf.
– It is recommended to start using sf for daily work.
– sf offers a simplified command taxonomy that reflects a developer’s workflow.
– Example: sf org create command replaces force:org:create and offers clearer intent.
3. Features of sf:
– sf includes visual and interactive commands, such as creating orgs with the ability to resume long-running operations.
– It offers a more streamlined and user-friendly experience.
4. Migrating to the sf executable:
– Besides switching the executable name from sfdx to sf, there are other changes to CLI commands when upgrading projects.
– The force topic has been removed from most commands.
– Topics, commands, and subcommands are now separated by spaces instead of colons.
– Example: sf org list replaces force:org:list.
5. Examples of common sfdx commands and their sf equivalents:
– The table provides examples of commands and their equivalent sf commands.
– Changes include the removal of the force topic, changes in subcommands, and changes in flag names.
– Example: sf org delete scratch replaces force:org:delete -p -u recipes, with changes in subcommand and flag names.
You can read it here: https://sfdc.blog/ViaoQ
Source from developer(dot)salesforce(dot)com