excluded-metadata flag on `sf project generate manifest` doesn't exclude all types

[NBray-VTG]

Summary

When running sf project generate manifest --from-org my-org --name package --excluded-metadata ReportType --excluded-metadata Dashboard --excluded-metadata Report I noticed it was only taking out the ReportType and not Reports and Dashboards from the generated package xml.

I reduced this to only attempt to exclude 1 option, and it would not exclude either of the two that failed before.
I went on and attempted CustomObject (which worked) and EmailTemplate (which did not work).
I suspect it might have something to do with types of metadata that can use the '*' wildcard in the manifest vs those that can't... if that helps any

Steps To Reproduce

I believe a full project would not be required, but rather an authorized org containing metadata mentioned above. (If you need me to make a repo for this I can, but since this only generates a manifest, I figured any org available to you would be sufficient)

1. Run sf project generate manifest --from-org {alias} --name package --excluded-metadata ReportType --excluded-metadata Dashboard --excluded-metadata Report --excluded-metadata CustomObject --excluded-metadata EmailTemplate

Expected result

No metadata listed for the 5 Metadata types specified

Actual result

Reports, Dashboards, and EmailTemplates remain listed in the package.xml

System Information

{
    "architecture": "darwin-arm64",
    "cliVersion": "@salesforce/cli/2.78.3",
    "nodeVersion": "node-v23.5.0",
    "osVersion": "Darwin 24.3.0",
    "rootPath": "~/.nvm/versions/node/v23.5.0/lib/node_modules/@salesforce/cli",
    "shell": "zsh",
    "pluginVersions": [
      "@oclif/plugin-autocomplete 3.2.21 (core)",
      "@oclif/plugin-commands 4.1.20 (core)",
      "@oclif/plugin-help 6.2.25 (core)",
      "@oclif/plugin-not-found 3.2.40 (core)",
      "@oclif/plugin-plugins 5.4.32 (core)",
      "@oclif/plugin-search 1.2.21 (core)",
      "@oclif/plugin-update 4.6.31 (core)",
      "@oclif/plugin-version 2.2.23 (core)",
      "@oclif/plugin-warn-if-update-available 3.1.33 (core)",
      "@oclif/plugin-which 3.2.29 (core)",
      "@salesforce/cli 2.78.3 (core)",
      "apex 3.6.8 (core)",
      "api 1.3.3 (core)",
      "auth 3.6.94 (core)",
      "custom-metadata 3.3.40 (user)",
      "data 4.0.11 (core)",
      "deploy-retrieve 3.20.0 (core)",
      "info 3.4.39 (core)",
      "limits 3.3.46 (core)",
      "marketplace 1.3.7 (core)",
      "org 5.2.32 (core)",
      "packaging 2.9.17 (core)",
      "schema 3.3.50 (core)",
      "settings 2.4.16 (core)",
      "sobject 1.4.50 (core)",
      "telemetry 3.6.33 (core)",
      "templates 56.3.38 (core)",
      "trust 3.7.65 (core)",
      "user 3.6.9 (core)"
    ]
  }

[github-actions]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[WillieRuemmele]

I'm not sure if it even depends on if the metadata supports wildcards... this things like something the CLI Should be able to filter out, regardless of the server-side support

[git2gus]

This issue has been linked to a new work item: W-17980476

[NBray-VTG]

@WillieRuemmele I agree. No idea if it has anything to do with it, that is just the commonality I found and thought I'd note that in case that ended up being relevant to fixing it.

[alexerhardt]

I am seeing the same issue, it's pulling in Documents which I am trying to exclude explicitly.

[shetzel]

@NBray-VTG @alexerhardt - This bug is specific to a type of metadata we refer to as "in folder metadata". Reports, documents, dashboards are all metadata contained by a folder, and the folder itself is metadata as well. Are you trying to exclude the (e.g.) documents but not the document folders or are you trying to exclude the documents and the document folders? If the latter, I would use --excluded-metadata DocumentFolder. That will exclude both due to how the listMetadata API works (which is used under the covers by the project generate manifest command). If you're trying to only exclude the document but not the document folder, what's the usecase for that? It would be an easy fix to exclude both the document and its folder but if you want to exclude them separately that is slightly more involved due to how the listMetadata API works.

[cristiand391]

this was fixed in latest, PR:
forcedotcom/source-deploy-retrieve#1535