Generates package.xml from the Unmanaged container/Managed Package or Changesets

generatepkgXML.sh

#!/bin/bash

if [ $# -lt 1 ]
then
    echo Usage: generatepkgXML.sh orgalias packageName
    exit
fi

## Retrieve the PackageXML from Unmanaged Container

sfdx force:mdapi:retrieve -s -r ./mdapipkg -u $1 -p "$2" # Retrieve Metadata API Source from Package Name

unzip -o -qq ./mdapipkg/unpackaged.zip -d ./mdapipkg # Unzip the file

rm -rf ./manifest/ # If manifest directory exists delete it

mkdir ./manifest/ # Create a New Manifest Directory

cp -a ./mdapipkg/package.xml ./manifest/ # Copy package.XML to manifest directory

rm -rf ./mdapipkg # Delete the mdapipkg source

Hi Shrivastava,

Regarding, the profiles and permission sets automated deployment into sandboxes and PROD through CICD.
While using scratch org model development, I could see that it is creating entire package of force-app directory, if entire force-app directory is deployed into any sandbox which would take more time to do the deployment right. Instead of that what would be easy approach to do deployment while using scratch orgs and
How are maintaining the code in Git repo like Feature branch(what it contains - Only feature changes or entire source code)
After creating a scratch org (empty) while pushing code the scratch org ( it's throwing many errors and we have more than 15000+ components certainly which are taking more time and failing to push). Need suggestion on move forward further at this point.
Thanks for your support and appreciate you.

@balanandam Scratch Org has limitation of 10k metadata components. Were you able to proceed, if so please share your journey too.

Hello Mohith,
I am trying to create package.xml for Salesforce CPQ only. Can you please please help me on this. I sincerely appreciate it.

Regards,
Goutam