Closed aheber closed 3 years ago
@mshanemc, sorry to mention you but realized this might be the wrong place for this. Should I move this to the CLI repo?
@aheber - this could be a recent regression with the SDR library. I think for most types this doesn't matter but for settings it does. I'll try to clean this up with some current work in progress I have but also create a separate issue for tracking.
This issue has been linked to a new work item: W-9852745
Thank you!
This is fixed now. Thanks @aheber!
It seems the SDR library is creating an invalid package.xml file when deploying all of the Settings metadata type. Including both
<members>*</members>
and another specific member, such as<members>Org</members>
produces this error in deploy "Cannot specify the wild card and specific Settings entities together in the manifest."If you take a clean project, create a fresh scratch org, retrieve the Org Settings (
sfdx force:source:retrieve -m Settings:Org
), and deploy all settings back (sfdx force:source:deploy -m Settings
) then the erroneous wildcard entry is added.This seem to be included as a catch-all and I didn't see this behavior when I was using the beta version of the plugin. (I recently updated our deployment environments that build scratch orgs). I have no idea how many other Metadata Types might have this limitation.
npm install
appears to fail due to being unable to resolve dependency versions. Aside from that I'm on Windows and the package commands don't appear to be Windows friendly.sfdx-cli/7.115.1 win32-x64 node-v14.17.5