generate manifest file using multiple package directories which can help --manifest based project deployment

[sambit-diff]

We started using multiple project directories taking reference from https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_ws_mpd.htm and our project structure looks as below:

project-repo
/force-app
/force-log
/force-integration
/manifest
package.xml
/destructiveChanges
destructiveChanges.xml
.. [other default project files]
sfdx-project.json

{ "packageDirectories": [ { "path": "force-app", "default": true }, { "path": "force-integration" }, { "path": "force-log" } ], "name": "project-repo", "replacements": [ { "filename": "/force-app/main/classes/ValidateMyClass.cls", "stringToReplace": "SFP_EXAMPLE_URL", //Added in APEX class for replacement "replaceWithEnv": "VAULT_EXAMPLE_URL" //Read from vault } ], "namespace": "", "sfdcLoginUrl": "https://login.salesforce.com", "sourceApiVersion": "61.0" }

Our deployment process is:

1. import key-value pair from vault or properties file for string replacement - this is not using any @salesforce/cli commands, a script is developed to update sfdx-project.json file, following the document https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_ws_string_replace.htm which will replace values from vault before deployment
2. salesforce generate manifest - this step executes command "sf project generate manifest --source-dir /project-repo/force-app --source-dir /project-repo/force-integration --name source-dir-package" and generates file 'source-dir-package.xml'
3. salesforce login
4. salesforce deploy - using command "sf project deploy start --target-org dev --manifest source-dir-package.xml --pre-destructive-changes manifest/destructiveChanges/destructiveChanges.xml --ignore-warnings --test-level RunLocalTests --junit --coverage-formatters json-summary --coverage-formatters cobertura --dry-run --wait 60 --ignore-conflicts"

In step 2, the output file is missing all metadata from 'force-integration' package directory. It only added 'force-app' components/metadata. This is why, during deploy command, only 'force-app' metadata is getting deployed. I am not sure if there is already a solution, but I couldn't find any. Please could you advice how generate manifest command pick all metadata from all package directories?

I have tried using generate manifest command --source-dir in multiple way, but no luck!!

[shetzel]

@sambit-diff - It would help to know the version of the CLI and plugins you're using but aside from that, it looks like your paths are wrong. If you're using relative paths then it's relative to the project and shouldn't begin with a /. So your command should be:
sf project generate manifest --source-dir force-app --source-dir force-integration --name source-dir-package. I just tried this with a multiple package directory project and it combined metadata from 3 different paths. I used CLI v2.78.3 which is latest.

[sambit-diff]

@shetzel thank you for replying back on this. I already tried this command, but it didn't work for me i.e., neither on azure pipeline, not or my local. It might be because of cli version. I am using v2.69.14 on agents, and v2.75.5 on local. I will update and try again, thank you