force:package:install. You can specify tests to run after deployment and indicate whether to roll back the deployment if there are errors.
force:source:convertcommand) as it will look at what is in the package.xml file to determine what is supposed to be deployed.
force:mdapi:deploycommand defaults to true.
force:package:version:createcommand. It needs a packageId (starts with 04t) or an alias from the local sfdx-project.json file as a parameter.
force:source:pushonly works on objects that are ‘trackable and in scratch orgs.
source:deploycommand works differently from source:push for scratch orgs. The source you deploy overwrites the corresponding metadata in your org, similar to running
source:pushwith the — force option. To deploy metadata that’s in the metadata format, use
source:retrieveare used to keep the org and sandbox up to date in terms of branching. Source:deploy and source:retrieve are used to actually push the metadata to another sandbox / environment.
<fullName>contains the name of the server-side package. If no
<fullName>exists, this is a client-side unpackagedpackage.
<types>contains the name of the metadata type (for example, CustomObject) and the named members (for example, myCustomObject__c) to be retrieved or deployed. You can add multiple
<types>elements in a manifest file.
<members>contains the fullName of the component, for example MyCustomObject__c. The
listMetadata()call is useful for determining the fullName for components of a particular metadata type, if you want to retrieve an individual component.
<name>contains the metadata type, for example CustomObject or Profile. There is one name defined for each metadata type in the directory. Any metadata type that extends Metadata is a valid value. The name that’s entered must match a metadata type that’s defined in the Metadata API WSDL.
<version>is the API version number that’s used when the .zip file is deployed or retrieved.