We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
running sgd against a project that contains some metadata types that should be included in the package.xml that is generated but these are skipped.
Bot BotVersion
sgd should detect these metadata types and include them in the package.xml :-)
Alternative is hand editing of the generated package.xml :-(
force-app/mainWhitelistOrigins .corsWhitelistOrigin-meta.xml .corsWhitelistOrigin-meta.xml
Package.xml
<types> <members>Virtual_Assistant</members> <members>Virtual_Assistant2</members> <name>Bot</name> </types> <types> <members>Virtual_Assistant.v1</members> <members>Virtual_Assistant2.v1</members> <name>BotVersion</name> </types>
The text was updated successfully, but these errors were encountered:
@scolladon Thank you in advance!
Sorry, something went wrong.
Please disregard the corsWhitelist item, I see that it's actually in there and working now!
@bobbywhitesfdc please look the new version 4.6.0 🥳
scolladon
Successfully merging a pull request may close this issue.
running sgd against a project that contains some metadata types that should be included in the package.xml that is generated but these are skipped.
Bot
BotVersion
Describe the solution you'd like
sgd should detect these metadata types and include them in the package.xml :-)
Describe alternatives you've considered
Alternative is hand editing of the generated package.xml :-(
Additional context
Here's the structure on the filesystem that I've seen:
force-app/main/default/bots/
.bot-meta.xml
.botVersion-meta.xml
force-app/mainWhitelistOrigins
.corsWhitelistOrigin-meta.xml
.corsWhitelistOrigin-meta.xml
Package.xml
The text was updated successfully, but these errors were encountered: