HANDBOOK.md

Source-Deploy-Retrieve (SDR) Handbook

Table of Contents

• Introduction
• Symbol Key
• Metadata Registry
  • Overview
  • Metadata registry file
  • Metadata registry entries
  • Updating the Metadata registry file
  • The registry object
  • Querying registry data
• Component Resolution
  • Overview
  • Resolving from metadata files
  • Resolving from a manifest file (package.xml)
  • Tree containers
    • Creating mock components with the VirtualTreeContainer
• Component Packaging
  • Overview
  • Converting metadata
  • The conversion pipeline
    • ComponentConverter
    • ComponentWriter
    • ConvertContext
    • In decomposedMetadataTransformer.ts
    • In convertContext.ts
• Component Merging
  • Overview
  • CustomObjects across multiple package directories
• Component Sets
  • Overview
  • Creating a set
  • Initializing a set from metadata files
  • Initializing a set from a manifest file
  • Lazy pipeline methods
• Deploying and Retrieving
  • Overview
  • Establishing an org connection
  • Deploying
    • Deploy with a source path
    • Deploy with a manifest file
    • Canceling a deploy
    • Make requests with an existing deploy
  • Retrieving
    • Retrieve with a source path
    • Retrieve with a manifest file
    • Canceling a retrieve
    • Make requests with an existing retrieve
• Further Examples

Introduction

The SDR library is a JavaScript toolkit for working with Salesforce metadata. It is the succeeding architecture of the source-driven development code in the force-com-toolbelt. The rewrite was designed with the following in mind: speed, memory efficiency, and modularity/“hackability“. We embrace these traits by using NodeJS streams, the latest developments in the NodeJS and Typescript ecosystem, and designing extendable interfaces.

Guiding Principles:

• Loosely coupled design - No assumptions are made about the consumers of the modules
• Solutions aren’t built for specific metadata types, but for classifications of types
  • “But wait, aren’t there implementations and behaviors coded for specific types?” Yes there technically are - which makes this statement a bit hypocritical. However, it’s more about having the mindset of developing against a classification rather than specific metadata types. It boils down to being able to unit test in isolation from the real data as well as leaving room for future types that might fall under the same classification as existing ones.
• Configuration driven to easily add new metadata types and change behavior of existing ones
• Consider speed and memory usage with every change made

SDR was built to accomplish the task of deploying and retrieving metadata. There are a few steps that take place during the entire deploy or retrieve process though, and the library makes a point to distinctly treat them as separate modules. You can generally think of each of these modules as a “stage” in a metadata operation’s pipeline. While the modules might have some dependencies with one another, they can also be used somewhat in isolation to perform more granular operations. This unlocks the potential to build more flexible metadata tooling, as well as support existing granular commands that the CLI already has - we did not want to build this for just a VS Code experience.

Symbol Key

💡 Idea - Improvements and interesting concepts that could be worth exploring more

🛠 Maintenance - Work that should be done sooner rather than later

📝 Note - An interesting tidbit of information that should be kept in mind

🧽 Refactor/Clean - Nice to tidy up. Not crucial, they’re just nit picky things that the author, Bryan, dislikes. If someone feels similarly about cleaning up then go forth and conquer

Metadata Registry

Module: https://github.com/forcedotcom/source-deploy-retrieve/tree/main/src/registry

Overview

The metadata registry is the foundation of the library. It is a module to describe available metadata types on the platform, provide metadata about them (metadata of metadata woah), and other configuration. It is based off of the describeMetadata() API call, which provides information such as a type’s file suffix, directory name of its component files, whether or not components live in a folder type, etc. Additional information may also be added to a type definition to support functionality in the library. Not only is it an index of metadata types, but it also contains indexes on properties of metadata types to increase performance on certain operations — more on this later.

Metadata registry file

The config file consists of a handful of different indexes.

types contains an entry for each supported metadata type. As already mentioned, these entries contain metadata the library relies on to perform a variety of operations that will be described [later](Breaking Down a Metadata Type Entry).

suffixes maps file suffixes to metadata type ids. When parsing a file path, we can examine the file suffix and use this index to map what type it belongs to, providing a performance optimization. Not every metadata type has an associated file suffix, for those we use the following index instead.

strictDirectoryNames maps type directory names to the matching metadata type id. Types listed here are required to have their files located in a path that has a folder ancestor with the assigned directory name. We cannot determine some types from a file path’s file suffix alone for a handful of reasons:

• A type doesn’t have an assigned file suffix. This is common for bundle types (LightningComponentBundle, WaveTemplateBundle, etc)
• Two exposed metadata types share a file suffix. This is an undesirable pattern in the library, and the only way to reconcile it is to force one of the types to require a strict parent. Break the tie by forcing the newest type to require a strict parent. CustomSite is an example of this.
• A type is exposed with a suffix by the name of xml - a reserved suffix. I’m looking at you EmailServicesFunction.

childTypes maps child component file suffixes to their parent’s type id. This helps when, for instance, we are parsing a decomposed component file such as a CustomField on a CustomObject. We are then able to quickly identify the parent type of the file. This is primarily beneficial for decomposed components but may have other uses in the future.

Updating the Metadata registry file

This file is large and luckily, not entirely crafted by hand. And because new metadata types are being added to the platform each release, we’ll need to update the Metadata registry file. The update-registry module in the scripts folder automatically updates the registry as best it can using a describeMetadata() call against a provided Salesforce org, without overwriting manual changes. It also attempts to update the indexes listed in the previous section. When generating a new version of the registry, it’s important to manually review the changes to ensure they make sense and aren’t destructive. When in doubt, test functionality with the new version. See Contributing Metadata Types to the Registry in the development README on how to invoke the script with Yarn.

🛠 Another issue is we are limited by the permissions and licenses of the org that we are running the update script on, which may return incomplete describe information. We need to address this as soon as possible to not run into type gaps between releases. This is being worked on as of 7/16/2021.

Breaking Down a Metadata Type Entry

Luckily we're able to automatically generate most metadata type entries without any human interaction. However, we sometimes get it wrong, or we can't account for a setting. When this happens, we'll need to manually update the registry to get the desired behavior.

There's a lot of options, and toggles that will affect what happens to a metadata type, below, we'll explain what each does, and more importantly, when you'd want to enable each one.

In SDR, a metadata type entry is required to have, at minimum, 2 values, the id and the name

• id The id is a unique identifier for the metadata type. It's usually the API name lowercased. For ApexClass this becomes, apexclass
• name The name is the API name of the metadata type, as you would see it, so ApexClass.

Now, for all the optional properties which define how the metadata type is converted, where it's stored, and how we can recognize it.

• aliasFor This is used as a redirect, whenever this type is requested, return the value of aliasFor instead.
• directoryName The directoryName is the name of the directory where components are located in a package. Continuing with the ApexClass type, this would be classes.
• folderContentType If the type is a folder type, which means it is made up multiple files inside a directory, this is the id of the type it is a container for. For <x>Folder this is set to <x>, the DashboardFolder type has folderContentType set to Dashboard
• folderType If the type is contained in folders, the id of the type that contains it. This is like the inverse of folderContentType the Dashboard metadata type has folderType set to DashboardFolder
• ignoreParentName This boolean, when set to true will ignore the parent's name when constructing this type's fullName. This is only set on the CustomLabel type, the child of CustomLabels.
• ignoreParsedFullName This is a boolean that dictates whether to ignore the fullName (see Component Resolution for a detailed breakdown of the fullName attribute) that's parsed from the file path. If set to true the metadata type's name will be used instead. This is set to true for CustomLabels
• isAddressable this is a boolean that determines if a metadata type is supported by the Metadata API and if it should be written to a manifest, this is used for CustomFieldTranslation.
• legacySuffix When converting/deploying source, this will update the suffix in the output or temporary directory (metadata format) Use this, along with additional suffix keys in the registry, to support incorrect suffixes from existing code. CustomPageWebLinks used to use the .custompageweblink suffix, now they use .weblink this property was added to maintain existing projects functionality
• strictDirectoryName The strictDirectoryName is a boolean that determines whether components MUST reside in a folder named after the type's directoryName
• suffix The suffix is the suffix of the metadata type file, which is also in the suffixes entry in the registry. You might be wondering why is this an optional property? Well, some types, such as LightningComponentBundles and Documents don't require a certain suffix, or are a "bundle" type which is made of multiple files and directories. For ApexClass, this is .cls
• supportsPartialDelete this boolean indicates whether or not partial pieces of metadata can be deleted. Imagine bundle types removing some, but not all of their components
• supportsWildcardAndName This boolean determines whether or not a type can be referred to by both the * and by name in a manifest. This is true for both CustomObject and DigitalExperienceBundle
• unaddressableWithoutParent This applies to child types, and if true will require the parent type to be included when deploying/retrieving the child type
• uniqueIdElements This is the xml attribute that acts as the unique identifier when parsing the xml, usually fullName
• xmlElementName This is the XML element name for the type in the xml file used for constructing child components.

The registry object

The library exports at the public API level a JavaScript object version of the Metadata registry file. This object is also used internally to reference registry data. If a consumer finds themselves needing references to metadata types or describe information, they can use this object:

import { registry } from '@salesforce/source-deploy-retrieve';

registry.types.apexclass.name === 'ApexClass'; // => true
registry.types.auradefinitionbundle.directoryName; // => 'aura'

📝 The registry object is “deeply frozen”, meaning none of its properties, even the nested ones, are mutable. This is to ensure that a consumer cannot change registry information in a process and potentially affect functionality.

Registry Variants

It's possible that the registry isn't what a user wants

• you're building a new type and want an easy way to test your registry changes
• you disagree with the choice made in the registry (ex: I wish PermissionSet was decomposed instead of a giant file)

There are two options available if you're in an sfdx project.

• registryCustomizations: add your own partial of the the registry that'll be merged into the registry. It's a json object just like the registry itself.
• registryPresets: SDR defines "preset" registryCustomizations and you say which ones you want applied. Each one is a partial, and you can have any or all of them by listing them. Names correspond to something in src/registry/presets, so your project file could use

  "registryPresets": ["decomposePermissionSetBeta", "decomposeSharingRulesBeta"]

if you want only those 2 presets.

The naming convention is decomposeFoo where Foo is the top-level metadata type, and refers to /presets/Foo.json.

This requires that any constructedRegistry know about your project directory. You'll see lots of code passing that around, and passing around constructed RegistryAccess to avoid getting the default if a custom one was already constructed.

Be careful when instantiating classes (ex: ComponentSet) that will default a Registry or RegistryAccess--make sure to pass in a registry to preserve customizations.

Updating presets If you do need to update a preset to make a breaking change, it's better to copy it to a new preset and give it a unique name (ex: decomposeFooV2). This preserves the existing behavior for existing projects with the old preset.

Querying registry data

While it’s perfectly fine to reference the registry export directly, the RegistryAccess class was created to make accessing the object a bit more streamlined. Querying types and searching the registry is oftentimes easier and cleaner this way and contains built-in checking for whether or not a metadata type exists. Here’s a comparison of using each:

import { RegistryAccess, registry } from '@salesforce/source-deploy-retrieve';

// we can optionally pass custom registry data to the constructor
const registryAccess = new RegistryAccess();

// query type by suffix
registryAccess.getTypeBySuffix('cls');
registry.types[registry.suffixes['cls']];

// child types
registryAccess.getTypeByName('CustomField');
registry.types[registry.childTypes['customfield']].children['customfield'];

// get strict directory types
registryAccess.getStrictFolderTypes();
Object.values(registry.strictDirectoryNames).map((typeId) => registry.types[typeId]);

📝 If you find yourself writing some logic that involves querying the registry, consider adding a new method to RegistryAccess. Even if it maybe won’t be used in another place again, it’s often easier to read and nice to keep query logic in the same place.

Component Resolution

Module: https://github.com/forcedotcom/source-deploy-retrieve/tree/main/src/resolve

Overview

Almost every operation consists of working with metadata components. SDR abstracts Salesforce metadata with the MetadataComponent Typescript interface. These are objects consisting of a fullName and type property, where type is an object pulled from the type index of the registry object. This allows us to easily access registry data of a type right from a component object. Constructing objects that adhere to the component interface is known as component resolution. It could be as simple as building the object yourself, or it could be through some other helper mechanism. The latter is more likely and these mechanisms are referred to as resolvers.

Resolving from metadata files

Constructing component objects from files is a core feature of the library. This is the basis of the source deploy and source retrieve commands of the VSCode extensions and the CLI. The MetadataResolver class walks files from a given file path and constructs SourceComponent instances. This class implements the MetadataComponent interface and contains additional properties and methods to work with the collection of files that belong to a component. These are also referred to as source-backed components, since the components have files associated with them.

import { MetadataResolver } from '@salesforce/source-deploy-retrieve';

const resolver = new MetadataResolver();
const components = resolver.getComponentsFromPath('/path/to/force-app');

// or a single component
const [apexClass] = resolver.getComponentsFromPath('/classes/MyClass.cls');
apexClass.fullName; // => 'MyClass'
apexClass.xml; // => '/classes/MyClass.cls-meta.xml'

Metadata types often follow a pattern of how files are structured for one of its components. For example, a component of an Apex class or Apex trigger follows this structure:

• [class name].[file suffix]
• [class name].[file suffix]-meta.xml

The resolver constructs components based on the rules of such a pattern. It takes advantage of the fact there aren’t very many unique patterns/classifications, and for each one there is a SourceAdapter implementation that is responsible for populating the properties of a component based on the rules. Types are assigned adapters with the strategies property of the type definition in registry configuration. See the adapters module for all of the available adapters for different type classifications. The resolver’s algorithm when walking a file is:

1. Determine the associated type by parsing the file suffix. Utilize the registry indexes to determine a type
2. If the type has a source adapter assigned to it, construct the associated adapter. Otherwise use the default one
3. Call the adapter’s getComponent() method to construct the source component

📝 CAREFULLY consider whether new adapters need to be added. Ideally, we should never have to add another one and new types should follow existing conventions to reduce maintenance burden.

🛠 Most types will not need an adapter assigned to them. Unfortunately, for those that do, it is a manual process at the moment to update the registry with the right configuration value. There is an ongoing effort to help automatically set the configuration as needed, but for now we will have to do this.

🧽 The name MetadataResolver is a relic from when it was the only resolver. A more apt name would be SourceResolver. For the sake of the guide and to avoid ambiguity, I’m going to call it the source resolver. If this ends up being confusing then change it.

Resolving from a manifest file (package.xml)

The ManifestResolver class parses a manifest file to construct components. Unlike resolving from files, this resolver does not construct source-backed components because a manifest tells us nothing about where files live. If you think about it, some operations don’t require local files at all, such as when retrieving components to a blank new project.

import { ManifestResolver } from '@salesforce/source-deploy-retrieve';

(async () => {
  const resolver = new ManifestResolver();
  const components = await resolver.resolve('/path/to/package.xml');
  components.forEach((c) => console.log(`${c.fullName} - ${c.type.name}`));
})();

📝 So if the manifest resolver doesn’t create source-backed components, how do the deploy/retrieve commands work that utilize a manifest? We’ll go over this in the section Initializing a set from a manifest file. Those objects have an initializer that combines the efforts of the source and manifest resolvers to do exactly that. Following the principles of the library, we make pieces of functionality as building block modules to support larger operations. A tool author may just want to build something that analyzes and manipulates manifest files, so we don’t tightly couple it with assumptions about deploying and retrieving.

Adapters

One of SDR's main goals and dogmas, is to be a metadata type generalist, meaning that it won't have to accommodate for a certain metadata type over another. We should be able to group metadata types into similar categories, or classes and handle them all. This works pretty well, but from some the options above you can see that we've had to make some compromises to handle certain types. CustomLabels, CustomFieldTranslations, and DigitalExperienceBundle have had settings created just for those types to function We're hoping, that as new metadata types get released, that they'll fall into one of these preexisting categories, and we'll already have the ability to handle any of their specific functionality. We'll continue to see examples of this as we look at the strategies that can be defined for each metadata type. These different strategies define how a metadata type is resolved and converted between source and metadata formats. These strategies are optional, but all have a default transformer, and converter assigned to them, which assumes nothing special needs to be done and that their source and metadata format are identical, link to these files. Luckily, lots of type use the default transformers and adapters.

The strategies property, of a metadatata type entry in the registry, can define four properties, the adapter,transformer,decompositon, and recomposition. How SDR uses these values is explained more in detail later on, but we'll go through each of the options for these values, what they do, what behavior they enable, and the types that use them.

The "adapters", or "source adapters", are responsible for understanding how a metadata type should be represented in source format and recognizing that pattern when constructing Component Sets

The defaultSourceAdapter

This adapter handles most of the types in the registry, this can be used when the metadata type follows the following pattern The default source adapter. Handles simple types with no additional content.

Example Structure:

foos/
├── foo.ext-meta.xml
├── bar.ext-meta.xml

Types that follow this pattern

Layouts, PermissionSets, FlexiPages and any other types that don't explicitly list an adapter

Example Structure:

layouts/
├── Broker__c-Broker Layout.layout-meta.xml

The bundleSourceAdapter

Like the name suggests, this adapter handles bundle types, so AuraDefinitionBundles, LightningWebComponents. A bundle component has all its source files, including the root metadata xml, contained in its own directory.

Example Structure:

 lwc/
 ├── myFoo/
 |   ├── myFoo.js
 |   ├── myFooStyle.css
 |   ├── myFoo.html
 |   ├── myFoo.js-meta.xml

The decomposedSourceAdapter

Handles decomposed types. A flavor of mixed content where a component can have additional -meta.xml files that represent child components of the main component. It's helpful to remember that in metadata format, CustomObjects, for example, are stored in a singular file, the adapters will rewrite that file into a directory that is easier to use in source-tracking, work with as a team, and easier to understand as a human.

Example Types:

CustomObject, CustomObjectTranslation

Example Structures:

objects/
├── MyFoo__c/
|   ├── MyFoo__c.object-meta.xml
|   ├── fields/
|      ├── a.field-meta.xml
|      ├── b.field-meta.xml
|      ├── c.field-meta.xml

The digitalExperienceAdapter

Source Adapter for DigitalExperience metadata types. This metadata type is a bundled type of the format.

🧽 This is an example of SDR extending one of the "classes of metadata" to add support for DigitalExperienceBundle. Ideally this adapter would've been named something without the specific metadata type in its name, but until another type comes along and uses this adapter it'll be ok.

Example Structure:

site/
├── foos/
|   ├── sfdc_cms__appPage/
|   |   ├── mainAppPage/
|   |   |  ├── _meta.json
|   |   |  ├── content.json
|   ├── sfdc_cms__view/
|   |   ├── view1/
|   |   |  ├── _meta.json
|   |   |  ├── content.json
|   |   |  ├── fr.json
|   |   |  ├── en.json
|   |   ├── view2/
|   |   |  ├── _meta.json
|   |   |  ├── content.json
|   |   |  ├── ar.json
|   ├── foos.digitalExperience-meta.xml
content/
├── bars/
|   ├── bars.digitalExperience-meta.xml

In the above structure the metadata xml file ending with "digitalExperience-meta.xml" belongs to DigitalExperienceBundle MD type. The "_meta.json" files are child metadata files of DigitalExperienceBundle belonging to DigitalExperience MD type. The rest of the files in the corresponding folder are the contents to the DigitalExperience metadata. So, in case of DigitalExperience the metadata file is a JSON file and not an XML file.

The matchingContentAdapter

This adapter is used for ApexClass or other types where there is a "content" file and an .xml file. In source-format, an ApexClass is made up of two files, the .cls which contains the actual code from the class, and an accompanying "meta" file

classes/
 ├── myApexClass.cls
 ├── myApexClass.cls-meta.xml

The mixedContentAdapter

Handles types with mixed content. Mixed content means there are one or more additional file(s) associated with a component with any file extension. Even an entire folder can be considered "the content".

Example Types:

StaticResources, Documents, Bundle Types

Example Structures:

staticresources/
├── data.resource
├── data.resource-meta.xml/

bars/
├── myBar.xyz
├── myBar.ext2-meta.xml

Transformers

So now that we're able to recognize different "classes" of metadata based on either their file structure, their extensions, matching files, or any of the adapters listed above, we can start to convert them from source, or metadata format, to the other SDR accomplishes this conversion with "Transformers" that will transform the metadata. Similar to how there was a default adapter that handled most of the metadata types, this is true for transformers as well, but because we've committed to doing all of this work on the client, we have to support some complicated types, and have a few more transformers to help handle the edge-case types. Each of these transformers implements two different methods, a toSourceFormat and toMetadataFormat which are both hopefully self-explanatory. In most cases the transformers follow the adapters naming conventions... so there's a

• decomposedMetadataTransformer
• staticResourceMetadataTransformer
• defaultMetadataTransfomer
• nonDecomposedMetadataTransformer

There are fewer transformers than adapters because many types that have different adapters can share a transformer. A Bundle type and a MatchingContent type (LWC and ApexClass) are written the same in metadata and source format, but they're recognized in different ways.

Decomposition

The Decomposition entry is rarely defined, but plays a large part in breaking down larger types into a more manageable state. There's two options that hopefully make sense with the types that set each of them.

topLevel

option is used for the Bot and CustomObjectTranslations types. These types have their children types stored at their top level directory. Below, the Bot is broken up, and each file is stored directly under its "parent" Bot entry. While in the next example, the CustomObject is broken apart, and each piece is stored in its own subfolder, underneath the parent object

Example Structures:

bots/
├── MyBot/
|   ├── MyBot.Bot-meta.xml
|   ├── MyBot.template-meta.xml

folderPerType

The folderPerType is used for CustomObjects where each child type has its own folder.

Example Structures:

objects/
├── MyFoo__c/
|   ├── MyFoo__c.object-meta.xml
|   ├── fields/
|      ├── a.field-meta.xml

Recomposition

This is a snowflake entry, and unfortunately is only used when working with CustomLabels. The only value this can be set to is: startEmpty which allows us to skip searching for and reading a parent's xml file.

Tree containers

A TreeContainer is an encapsulation of a file system that enables I/O against anything that can be abstracted as one. The implication is a client can resolve source-backed components against alternate file system abstractions. By default for most operations, the NodeFSTreeContainer is used, which is simply a wrapper of the Node file system api calls. There is also the ZipTreeContainer, which is used for scanning components against the central directory of a zip file, and the VirtualTreeContainer, helpful for creating mock components in testing scenarios. This concept is central to how we resolve and extract components in a retrieved zip file.

Clients can implement new tree containers by extending the TreeContainer base class and expanding functionality. Not all methods of a tree container have to be implemented, but an error will be thrown if the container is being used in a context that requires particular methods.

💡The author, Brian, demonstrated the extensibility of tree containers for a side project by creating a GitTreeContainer. This enabled resolving components against a git object tree, allowing us to perform component diffs between git refs and analyze GitHub projects. This could be expanded into a plugin of some sort.

Creating mock components with the VirtualTreeContainer

If a consumer needs to create fake components for testing, the VirtualTreeContainer is a great way to do so without having to create real local files in a project. This is how the library tests its own functionality in fact.

import { ComponentSet, registry, VirtualDirectory, VirtualTreeContainer } from '@salesforce/source-deploy-retrieve';

// resolve components of a virtual tree
const virtualTree = new VirtualTreeContainer([
  {
    dirPath: '.',
    children: ['MyClass.cls', 'MyClass.cls-meta.xml', 'folder2'],
  },
  {
    dirPath: '/folder2',
    children: ['MyClass2.cls', 'MyClass2.cls-meta.xml'],
  },
]);
const components = ComponentSet.fromSource({
  fsPaths: ['.'],
  tree: virtualTree,
});
components.toArray(); // => [<MyClass>, <MyClass2>]

// create an individual component
const virtualFs: VirtualDirectory[] = [
  {
    dirPath: '/metadata',
    children: [
      {
        name: 'MyLayout.layout',
        data: Buffer.from('<Layout></Layout>'),
      },
    ],
  },
];
const layout = SourceComponent.createVirtualComponent(
  {
    name: 'MyLayout',
    type: registry.types.layout,
    xml: '/metadata/MyLayout.layout',
  },
  virtualFs
);

console.log(await layout.parseXml()); // => "<Layout></Layout>"

Component Packaging

Module: https://github.com/forcedotcom/source-deploy-retrieve/tree/main/src/convert

Overview

Another key building block for deploying and retrieving is copying metadata files to or from a zip file. The component packaging functionality is responsible for this aspect. It also handles the SFDX concept of converting files between source and metadata format (see Salesforce DX Project Structure and Source Format) Not only is it used during deploys and retrieves, but also in isolation for various other use cases — think of the CLI convert commands.

Converting metadata

We can resolve, convert, and copy metadata using the [MetadataConverter](https://github.com/forcedotcom/source-deploy-retrieve/blob/main/src/convert/metadataConverter.ts) class. Because we’re dealing with files here, the components must be source-backed to perform the operation.

import {
    MetadataConverter,
    MetadataResolver
} from '@salesforce/source-deploy-retrieve'

const resolver = new MetadataResolver();
const converter = new MetadataConverter();

(async () {
    // sfdx force:source:convert
    // resolve a source format package and convert
    const components = resolver.getComponentsFromPath('/path/to/force-app');
    await converter.convert(components, 'metadata', {
        type: 'directory',
        outputDirectory: '/path/to/output',
        packageName: 'MetadataFormatPackage'
    });

    // sfdx force:mdapi:convert
    // resolve a metadata format package and convert
    const components = resolver.getComponentsFromPath('/path/to/force-app');
    await converter.convert(components, 'source', {
        type: 'directory',
        outputDirectory: '/path/to/output',
        packageName: 'SourceFormatPackage'
    });
})();

🛠🧽 Most of this code lives in the convert module and makes assumptions that file conversion between the two formats is happening. This is a relic that never was addressed but should be, because it’s reasonable to want to copy files without the conversion process. Think of the CLI mdapi deploy and mdapi retrieve commands - these don’t do anything special with conversion regarding files. We might look into renaming exports to not assume conversion is happening and update the API to allow conversion to be optional.

The conversion pipeline

When convert is called, the method prepares the inputs for setting up the conversion pipeline. The pipeline consists of chaining three custom NodeJS stream, one for each stage of the copy operation. To more deeply understand what is happening in the conversion process, it’s recommended to familiarize yourself with streaming concepts and the NodeJS API. See Stream NodeJS documentation and Understanding Streams in NodeJS.

ComponentConverter

Here is where file transformation is done, but without being written to the destination yet. Similar to how source resolution uses adapters to determine how to construct components for a type (see The resolver constructs components based…), conversion uses MetadataTransformer implementations to describe the transformations. As you might guess, types are assigned a transformer, if they need one, in their metadata registry definition, otherwise the default one is used. Each transformer implements a toSourceFormat and a toMetadataFormat method, which are called by the ComponentConverter based on what the target format is. The methods will return a collection of WriteInfo objects, which as we’ve been touching on are “descriptions” of how to write a given file.

Let’s say we’re converting a Layout from source format to metadata format. The write infos returned would look something like this:

const xmlFile = component.xml; // path/to/source/MyLayout.layout-meta.xml
return [
  {
    // this is a Readable stream of the file's contents
    source: component.tree.stream(xmlFile),
    output: '/path/to/destination/MyLayout.layout',
  },
];

notice how we are stripping the -meta.xml suffix with the returned write info. This is essentially what’s happening in the DefaultMetadataTransformer. Once the converter has collected the write infos for a component, it pushes them to the write stage.

📝 In a perfect world, no transformation of metadata files would be necessary. This aspect exists because that’s how SFDX was designed. Having a tooling client do fancy things to files is prone to error and consistency across other tools when the API should be returning files in a source friendly format to begin with. Just like the source adapters, CAREFULLY CAREFULLY consider if another transformer needs to be created — the right answer is likely NO. We don’t want to create special logic for any more types.

ComponentWriter

A ComponentWriter is responsible for taking the write infos created in the previous stage and using them to finally write files to a destination. The library relies on two different implementations of a writer:

• StandardWriter - Pipes a write info’s readable source to a NodeJS fs.createWriteStream writable, saving the contents of the file to the output location on disk.
• ZipWriter - Pipes a write info’s readable source into a zip archive. This archive can either be written to disk or built in-memory, the latter of which is used for deploy operations as an optimization.

The strategies used here are consciously attempting to reduce I/O and memory utilization as much as possible, and we do so with the help of the NodeJS streams API again. For instance, having the zip buffer built right in memory for a future deploy operation helps with this. Before, we were copying files to disk, then zipping those files and writing the result to disk, and then finally reloading the zip back into memory. This can be expensive on slower machines and grows a bit fast regarding time/space complexity.

ConvertContext

If you’ve been examining the code, you may have noticed the component converter holds on to something called a ConvertContext. This object is meant to be used as a “global state” of sorts over the course of a single conversion. Transformers can access this object in their implementation to save state and establish context of previous work they have already completed through subsequent calls. The state is stored in objects that extend ConvertTransactionFinalizer. A convert context has an instance of each of these finalizers to represent a section of state. Different scenarios may depend on different shapes of state, so we use these objects to isolate those states.

Once finalizers have state data set, it needs to be processed at the end of the convert. The metadata converter implements the _flush() method, which is defined by the NodeJS streaming API to run any other final logic after a stream has been signaled as finished, or in our terms no more components are to be processed. This is where we call the finalize() methods of each convert transaction finalizer to push any leftover write infos that need to be created from the state.

In less general terms, this concept was created out of necessity to support converting decomposed components like CustomObjects. When processing a CustomObject, we need to combine the contents of all of its files, which are components themselves, into a single file for deployment. If we are processing a CustomField in the pipeline, we don’t want to tell the component writer to write a file just yet because we’re still waiting on any other child components of the same object to be included in the file. So instead of returning a write info, we save the same information in the RecompositionFinalizer’s state. Once all components of the convert have been processed, RecompositionFinalizer.prototype.finalize() is called to combine all of an object’s child components into a single write info, and to push that to the component writer.

In decomposedMetadataTransformer.ts

// in decomposedMetadataTransformer.ts

public async toMetadataFormat(component: SourceComponent): Promise<WriteInfo[]> {
    // If the component we're processing has a parent (like CustomObject),
    // it's assumed to be a child (like CustomField)
    if (component.parent) {
        this.context.recomposition.setState((state) => {
            if (state[parentName]) {
                // Add the child component if we already have an entry for parent
                state[parentName].children.add(component);
            } else {
                // Create a new entry in the state, mapping the parent component
                // to an array of children to be rolled up in the result
                state[parentName] = {
                    component: component.parent,
                    children: new ComponentSet([component], this.registry),
                };
            }
        });
    }

    // ... other code

    // Don't return any write infos - we're not ready to write files yet!
    return []
}

In convertContext.ts

class RecompositionFinalizer extends ConvertTransactionFinalizer<RecompositionState> {
  protected _state: RecompositionState = {};

  public async finalize(): Promise<WriterFormat[]> {
    const writerData: WriterFormat[] = [];

    for (const { component: parent, children } of Object.values(this.state)) {
      // Combine the children with the parent to create one XML object
      const recomposedXmlObj = await this.recompose(children, parent);
      writerData.push({
        component: parent,
        // Return one write info per CustomObject that is the combined result
        writeInfos: [
          {
            source: new JsToXml(recomposedXmlObj),
            output: join(parent.type.directoryName, `${parent.fullName}.${parent.type.suffix}`),
          },
        ],
      });
    }

    return writerData;
  }
  // ...
}

📝 Does this sound a bit overcomplicated? I think it does. These are the kinds of things we have to create though to accommodate the fact that we committed to the client being responsible for fancy file transformations. If the server returned a CustomObject already in an “IDE editing/git friendly“ format we would not have to do this.

Component Merging

Overview

Component merging refers to replacing the files of one component with the files of another that share the same fullName and type pair. This technique is used when retrieving components to an SFDX project that has local versions of the same components. In effect, we can overwrite a component’s files in a project with those from a matching component’s files from the retrieved zip archive.

The following is an example of what a retrieve call is more or less doing under the hood when extracting components to an existing project:

import { MetadataConverter, MetadataResolver, ZipTreeContainer } from '@salesforce/source-deploy-retrieve';

(async () => {
  // Resolving components in the zip file
  const zipBuffer = getZipBuffer();
  const zipTree = await ZipTreeContainer.create(zipBuffer);
  const zipResolver = new MetadataResolver(undefined, zipTree);
  const zipComponents = zipResolver.getComponentsFromPath('.');

  // Resolving components in SFDX project
  const resolver = new MetadataResolver();
  const forceAppComponents = resolver.getComponentsFromPath('/path/to/force-app');
  const testAppComponents = resolver.getComponentsFromPath('/path/to/test-app');

  const converter = new MetadataConverter();
  const result = await converter.convert(zipComponents, 'source', {
    type: 'merge',
    mergeWith: packageDirComponents,
    // If a component can't be merged, put it here by default
    defaultDirectory: '/path/to/force-app',
  });
})();

SDR does not have an abstraction of an SFDX package directory. The goal at first was to come up with the underlying concept of replacing a component’s files with another matching component’s, rather than be confined to the idea of a package directory. If you find yourself asking “how do multiple package directories work”, component merging is the answer. If you resolve components in every package directory of a project and utilize that result when performing a merge, you are in effect handling the multiple package directory scenario. This doesn’t mean we can’t introduce a package directory abstraction into the library if it proves to be useful however.

CustomObjects across multiple package directories

Component merging also handles the scenario where we split a CustomObject across multiple package directories. For instance, one package has all the custom fields, while another contains the object itself. When we retrieve the CustomObject from the org, the SFDX behavior is to put the fields in one package directory, and the rest of the object in another.

Let’s say in this scenario the object we’re working with is MyObj__c

• Resolve components across every package directory in the project
• Two source-backed components representing the same fullName and type pair will be resolved, one for the group of fields, one for the object itself. The library essentially interprets it as two versions of the same component
• Components pass through the conversion pipeline with the merge option specified
• Even though they map to the same component, each copy of it is passed through the DecomposedMetadataTransformer
• Since each copy has different components in it (CustomFields in one, other stuff in other), the transformer will know how to set the output of each write info for the component it’s actually converting, which itself is fully composed.

Component Sets

Module: https://github.com/forcedotcom/source-deploy-retrieve/tree/main/src/collections

Overview

Oftentimes we need to work with a unique collection of components. A ComponentSet automatically de-dupes components and allows us to test whether or not a particular component is a member of a set. They also provide convenience methods that wrap the other functionality of the library, making it the easiest entry point for the most common use cases.

Creating a set

Component sets key components using their fullName and type id, i.e. only one pair will ever be present in the set. This implies that anything that conforms to the MetadataComponent interface can be added to a set. SourceComponents in fact have particular logic on how they are stored. While only one fullName and type pair can be present in a set, multiple source-backed components can map to the same pair under-the-hood. This is how splitting a CustomObject across multiple package directories is achieved - by treating each version of the component as a separate source-backed component that points to the same fullName and type pair in a set. When component merging happens, the conversion logic is able to combine the source components belonging to the same pair.

The easiest way to build ComponentSets is by using the ComponentSetBuilder class's static build() function. See https://github.com/forcedotcom/source-deploy-retrieve/tree/main/src/collections/componentSetBuilder.ts for details. Simply pass a configuration object to build() and it takes care of the rest, including handling destructive changes!

Let’s look at some examples of adding components and testing membership:

import { ComponentSet, MetadataResolver } from '@salesforce/source-deploy-retrieve';

const set = new ComponentSet();
set.add({ fullName: 'MyClass', type: 'ApexClass' });
set.add({ fullName: 'MyLayout', type: 'Layout' });
set.size; // => 2
set.add({ fullName: 'MyClass', type: 'ApexClass' });
set.size; // => 2

const resolver = new MetadataResolver();
const mixedComponentTypes = new ComponentSet([
  { fullName: 'MyLayout', type: 'Layout' },
  { fullName: 'MyComponent', type: 'LightningComponentBundle' },
]);

const [myClass] = resolver.getComponentsFromPath('/path/to/classes/MyClass.cls');
mixedComponentTypes.add(myClass);
mixedComponentTypes.size; // => 3
mixedComponentTypes.has({ fullName: 'MyClass', type: 'ApexClass' }); // => true

Initializing a set from metadata files

Up to this point, we have demonstrated resolving source-backed components using the MetadataResolver. Another option is to use the fromSource static initializer, which wraps the resolver, calls it, adds the result to a new set, and returns that set. This is often more convenient than constructing things yourself to produce the same result. The reason why the library encourages either way to resolve source-backed components is because there may be some slight trade-offs depending on which is used. Constructing a component set adds some overhead due to the work of ensuring uniqueness, but it’s very possible that it’s a tolerable/negligible amount of extra time for a consumer. Therefore, the recommendation is as follows:

• Use a component set initializer to resolve components if you intend to perform a common operation that requires a unique collection - deploying, retrieving, package xml generation, etc
• Use the resolver directly if you purely want to do some component analysis that doesn’t require a unique collection

import { ComponentSet } from '@salesforce/source-deploy-retrieve';

const fromOnePath = ComponentSet.fromSource('/path/to/force-app');

// Resolve components from each path
const fromMultiplePaths = ComponentSet.fromSource([
  '/path/to/force-app',
  '/path/to/test-app',
  '/path/to/helper/main/default/classes',
]);

(async () => {
  // Resolve all Layout components in the zip file
  const zipTree = await ZipTreeContainer.create('/path/to/package.zip');
  const filter = new ComponentSet([{ fullName: '*', type: 'Layout' }]);
  const withOptions = ComponentSet.fromSource({
    fsPaths: ['.'],
    tree: zipTree,
    include: filter,
  });
})();

Initializing a set from a manifest file

Similar to how fromSource is a wrapper for the source resolver, fromManifest is a wrapper for the ManifestResolver. By default it does not add source-backed components, but using an options object we can use the resolved manifest as a filter for resolving them. An admittedly tricky aspect of this initializer is how to behave when a wildcard member is encountered in the file. These are the scenarios along with sub-bulleted reasons why they exist:

• If not resolving source, add the wildcard as a component to the set by default
  • When performing a retrieve independent of a project context
  • To accurately express the contents of the manifest file
• If resolving source, do NOT add the wildcard as a component to the set by default
  • When deploying. We cannot deploy a literal wildcard
  • When only wanting to use the wildcard as a means to filter components as a particular type, without expressing itself as a component
• If resolving source, add the wildcard as a component to the set with forceAddWildcard: true
  • When retrieving in the context of a project. We want every component of the type in an org, as well as to resolve any source-backed ones in the project
  • When wanting to use the wildcard as not only a filter when resolving source components, but also to express it as a component itself

Here are examples of the above scenarios:

import { ComponentSet } from '@salesforce/source-deploy-retrieve';

/**
 * /path/to/package.xml
 *
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>TestPropertyController</members>
        <members>TestSampleDataController</members>
        <name>ApexClass</name>
    </types>
    <types>
        <members>Broker__c</members>
        <name>CustomObject</members>
    </types>
    <types>
        <members>*</members>
        <name>ApexTrigger</members>
    </types>
    <version>50.0</version>
</Package>
*/

(async () => {
  // Resolve non-source-backed components from the manifest
  const simple = await ComponentSet.fromManifest('/path/to/package.xml');
  simple.size; // => 4 (wildcard member is added as its own component)

  // Resolve source-backed components with a manifest
  const manifestWithSource = await ComponentSet.fromManifest({
    manifestPath: '/path/to/package.xml',
    resolveSourcePaths: ['/path/to/force-app', '/path/to/force-app-2'],
  });
  manifest.size; // => 6 (assume 2 triggers in force-app, 1 trigger in force-app-2)

  // Same as previous example, but add the wildcard as its own component
  const manifestWithSource = await ComponentSet.fromManifest({
    manifestPath: '/path/to/package.xml',
    resolveSourcePaths: ['/path/to/force-app', '/path/to/force-app-2'],
    forceAddWildcards: true,
  });
  manifest.size; // => 7 (including { fullName: '*', type: 'ApexTrigger' } now)
})();

Lazy pipeline methods

Component sets contain similar methods to those found on JavaScript Arrays, such as map and filter, as well as others like first(), find(), and filter(). These are obtained from extending the LazyCollection class. The only key difference with arrays is that these use iterators to lazily process components, meaning that components will pass through an entire chain before the previous component.

import { ComponentSet } from '@salesforce/source-deploy-retrieve'

// Get paths to all of the classes with "Test" in the name
const testClassPaths = ComponentSet
    .fromSource('/path/to/force-app')
    .filter({ fullName } => fullName.includes('Test'))
    .map({ content } => content)
    .toArray();

Deploying and Retrieving

Module: https://github.com/forcedotcom/source-deploy-retrieve/tree/main/src/client

Overview

The order in which we’ve examined the concepts up to this point has been intentional. They are the building blocks leading up to the core use case of the library: deploying and retrieving. For a deploy, we must resolve source-backed components, then convert them into metadata format, write their files to a zip file, and finally send it to the org using the Metadata API. For a retrieve, we must resolve a mix of source-backed and non-source-backed components to make the Metadata API request, and once it finishes we resolve the components in the zip, convert them to source format, and finally copy them to a destination.

Metadata API deploys and retrieves are asynchronous operations. Once a request has been made, the status of the operation needs to be polled to determine whether or not the request has finished processing. This lifecycle is encapsulated with the MetadataApiDeploy and MetadataApiRetrieve classes — one instance is meant to map to one operation. They expose useful methods to process the lifecycle and make other requests, which will be illustrated later. These both extend MetadataTransfer in order to share common functionality such as polling.

The most common and simplest way to deploy and retrieve metadata is by using a Component Set. The easiest way to build ComponentSets is by using the ComponentSetBuilder class's static build() function. See https://github.com/forcedotcom/source-deploy-retrieve/tree/main/src/collections/componentSetBuilder.ts for details.

Establishing an org connection

Before we can perform either operation, we must establish a connection to an org. The library utilizes sfdx-core connection objects to do. Currently there are two options when using SDR — either the consumer supplies a connection instance themselves or they pass an org username. The former requires authentication to have been persisted in ~/.sfdx at some point prior. This is typically done by authorizing an org through the CLI or the VS Code extensions.

import { AuthInfo, Connection } from '@salesforce/core';

(async () => {
  // when passing only a username to deploy/retrieve operations, this
  // is happening under the hood
  const connection = await Connection.create({
    authInfo: await AuthInfo.create({
      // requires having already authenticated to this org
      username: '[email protected]',
    }),
  });
})();

See Connection in the API documentation for a more comprehensive overview of the object and how to use it. If a consumer is interested in authenticating an org outside of these two tools or customizing a Connection object, refer to that documentation.

Deploying

The simplest way to kick off a new deploy is through a component set. ComponentSet.prototype.deploy() takes every source-backed component in the set and starts a new deploy operation with the target org. It returns a promise that resolves a new MetadataApiDeploy. **** Technically if nothing goes wrong with the deployment, there is nothing more to do. Naturally though we’d like to monitor the progress and process the result. We can do this by attaching a listener to the update event and call pollStatus() to wait for the operation to finish.

📝 Keep in mind that when the deploy() promise resolves, it does NOT mean the deploy has finished. It means the request has been sent to the org. Remember, these are asynchronous operations.

Deploy with a source path

import { ComponentSet } from '@salesforce/source-deploy-retrieve';

(async () => {
  // Deploy every component in the classes folder
  const deploy = await ComponentSet.fromSource('/path/to/force-app/main/default/classes').deploy({
    usernameOrConnection: '[email protected]',
  });

  // Attach a listener to check the deploy status on each poll
  deploy.onUpdate((response) => {
    const { status, numberComponentsDeployed, numberComponentsTotal } = response;
    const progress = `${numberComponentsDeployed}/${numberComponentsTotal}`;
    const message = `Status: ${status} Progress: ${progress}`;
  });

  // Wait for polling to finish and get the DeployResult object
  const result = await deploy.pollStatus();

  // Output each file along with its state change of the deployment
  console.log(result.getFileResponses());
})();

Deploy with a manifest file

import { ComponentSet } from '@salesforce/source-deploy-retrieve';

(async () => {
  // Collect all components that are members of the manifest across
  // two different package directories
  const set = await ComponentSet.fromManifest({
    manifestPath: '/path/to/package.xml',
    resolveSourcePaths: ['/path/to/force-app', '/path/to/force-app-2'],
  });

  // Start a deploy with the components
  const deploy = await set.deploy({ usernameOrConnection: '[email protected]' });

  // Attach a listener to check the deploy status on each poll
  deploy.onUpdate((response) => {
    const { status, numberComponentsDeployed, numberComponentsTotal } = response;
    const progress = `${numberComponentsDeployed}/${numberComponentsTotal}`;
    const message = `Status: ${status} Progress: ${progress}`;
    console.log(message);
  });

  // Wait for polling to finish and get the DeployResult object
  const result = await deploy.pollStatus();

  // Output each file along with its state change of the deployment
  console.log(result.getFileResponses());
})();

Canceling a deploy

The Metadata API supports canceling a deploy in progress, and that is exposed through the cancel() method on the transfer object. Cancelations are also asynchronous operations - we need to poll to monitor when a cancelation actually finishes.

import { ComponentSet } from '@salesforce/source-deploy-retrieve';

(async () => {
  const deploy = await ComponentSet.fromSource('/path/to/force-app').deploy({
    usernameOrConnection: '[email protected]',
  });

  deploy.onUpdate(({ status }) => console.log(`Status: ${status}`));

  // send a cancel request to the org
  await deploy.cancel();

  // Wait until the cancelation finishes
  const result = await deploy.pollStatus();

  if (result.response.status === RequestStatus.Canceled) {
    console.log('The deploy operation was canceled');
  }
})();

Make requests with an existing deploy

If a deploy was started by some other client or routine, as long as we have the deploy ID we can still make requests to monitor the status or cancel the operation. This is done by constructing a MetadataApiDeploy object with the ID as an option.

import { MetadataApiDeploy } from '@salesforce/source-deploy-retrieve';

(async () => {
  const deploy = new MetadataApiDeploy({
    id: '00t12345678',
    usernameOrConnection: '[email protected]',
  });

  // check the status once without polling
  const { status } = await deploy.checkStatus();

  let message;

  switch (status) {
    case RequestStatus.Succeeded:
      message = 'Deploy has finished successfully';
      break;
    case RequestStatus.Failed:
      message = 'Deploy failed';
      break;
    case RequestStatus.Canceled:
      message = 'Deploy was canceled';
      break;
    default:
      message = 'Deploy is still in progress';
  }
})();

Retrieving

The simplest way to kick off a new retrieve is through a component set. ComponentSet.prototype.retrieve() will request every fullName and type pair in the set to be retrieved from the org to the specified output path. In order to have the components extracted to their destination, we are required to call the pollStatus() method. This will wait until the retrieve has finished and then convert and extract the files.

We also have the option of merging components that are retrieved in the org with those that are present in the set. Merging is required when retrieving existing components in an SFDX project. See Component Merging for more information about the concept. When the option merge: true is set, the files of the retrieved components are written to the locations of the files of the source-backed components in the set. For any non-source-backed components in the set, or if merge: false, these files are by default copied to the destination specified with the output option.

📝 Keep in mind that when the retrieve() promise resolves, it does NOT mean the retrieve has finished. It means the request has been sent to the org. Remember - these are asynchronous operations.

Retrieve with a source path

import { ComponentSet } from '@salesforce/source-deploy-retrieve';

(async () => {
  // Retrieve every component in the classes folder to the same location
  const retrieve = await ComponentSet.fromSource('/path/to/force-app/main/default/classes').retrieve({
    usernameOrConnection: '[email protected]',
    // default location if retrieved component doesn't match with one in set
    output: '/path/to/force-app',
    merge: true,
  });

  // Attach a listener to check the retrieve status on each poll
  retrieve.onUpdate(({ status }) => console.log(`Status: ${status}`));

  // Wait for polling to finish and get the RetrieveResult object
  const result = await deploy.pollStatus();

  // Output each retrieved file
  console.log(result.getFileResponses());
})();

Retrieve with a manifest file

import { ComponentSet } from '@salesforce/source-deploy-retrieve';

(async () => {
  // Collect all components that are members of the manifest across
  // two different package directories
  const set = await ComponentSet.fromManifest({
    manifestPath: '/path/to/package.xml',
    resolveSourcePaths: ['/path/to/force-app', '/path/to/test-app'],
    // We want to retrieve everything in the org as well,
    // see the section on initializing a set from a manifest file
    forceAddWildcards: true,
  });

  // Start a retrieve with the components
  const retrieve = await set.retrieve({
    usernameOrConnection: '[email protected]',
    // default location if retrieved component doesn't match with one in set
    output: '/path/to/force-app',
    merge: true,
  });

  // Attach a listener to check the retrieve status on each poll
  retrieve.onUpdate(({ status }) => console.log(`Status: ${status}`));

  // Wait for polling to finish and get the RetrieveResult object
  const result = await retrieve.pollStatus();

  // Output each retrieved file
  console.log(result.getFileResponses());
})();

Canceling a retrieve

Unlike deploys, there isn’t a mechanism for signaling a retrieve cancelation with the Metadata API. The library will simply break any potential polling of the retrieved status, and that is exposed through the cancel() method on the transfer object.

import { ComponentSet } from '@salesforce/source-deploy-retrieve'

(async () => {
    const retrieve = await ComponentSet
        .fromSource('/path/to/force-app')
        .retrieve({
            usernameOrConnection: '[email protected]'
            output: '/path/to/retrieve/output'
        });

    retrieve.onUpdate(({ status }) => console.log(`Status: ${status}`));

    // Start polling for the retrieve result
    retrieve.pollStatus().then(result => {
        if (result.response.status === RequestStatus.Canceled) {
            console.log('The retrieve operation was canceled');
        }
    });

    // stop polling for the retrieve result
    await retrieve.cancel();
})();

Make requests with an existing retrieve

If a retrieve was started by some other client or routine, as long as we have the retrieve ID we can still make requests to monitor the status or cancel the operation. This is done by constructing a MetadataApiRetrieve object with the ID as an option.

import { MetadataApiRetrieve } from '@salesforce/source-deploy-retrieve';

(async () => {
  const retrieve = new MetadataApiRetrieve({
    id: '00t12345678',
    usernameOrConnection: '[email protected]',
    output: '/path/to/retrieve/output',
  });

  // Wait for the existing retrieve to finish, and then extract the components
  const result = await retrieve.pollStatus();

  console.result(result.getFileResponses());
})();

Further Examples

For more code snippet examples similar to those found here, see the examples folder of the repository.