Support for GenAiPlannerBundle metadata type anywhere

[gnemiq]

Is your proposal related to a problem?

Yes. Currently, it looks like SGD doesn’t support the genAiPlannerBundle metadata changes when it’s placed outside the default folder structure (e.g. force-app/main/default/service/live-chat/genAiPlannerBundle/ServiceAgent/ServiceAgent.genAiPlannerBundle instead of the default force-app/main/default/genAiPlannerBundles/ServiceAgent/ServiceAgent.genAiPlannerBundle).

When running the sfdx sgd:source:delta command, SGD includes the GenAiPlannerBundle metadata in the package.xml it generates, but it fails to recognise it when generating the change sources folder/zipped directory, which causes the deployment to break with this error:

An object 'ServiceAgent' of type GenAiPlannerBundle was named in package.xml, but was not found in zipped directory

Describe a solution you propose

SGD plugin to capture genAiPlannerBundle changes that placed outside the default folder structure when running the sfdx sgd:source:delta command, so that the discrepancies between package.xml and changed sources folder/zipped directory can be eliminated.

Describe alternatives you've considered

Deploying the genAiPlannerBundle metadata manually outside of CI/CD

Additional context

Installation Command: sfdx plugins:install sfdx-git-delta
Salesforce Project API Version: 60.0

[scolladon]

Hi @gnemiq!

Thanks for raising this issue and thanks for contributing in making this project better!

For us, this metadata kind is an InResource type, meaning it have a -meta.xml file and a folder containing its sources or a file containing its definition (here the .genAiPlannerBundle file).
This kind of metadata works like StaticResources for example. It is not easily possible to know what files to look in advance and if a file in this metadata has changed then all its files should be deployed.
This is why for this kind of metadata it is required to put them inside their dedicated subfolder, it allows the plugin to detect its kind.

This could be improved with a simple algorithm :

1. Try matching the extension of the changed/added/deleted file to match with a metadata kind, if no match go next step
2. Try matching extension of files on the same folder, if no match go next step
3. Go one directory up in the hierarchy and go step 2

Though it would be hard for deleted metadata as it would require traverse the hierarchy at the from git revision so we can deduce its kind. It would be way slower in the worst case scenario IMHO.

In your particular case it may be possible to fix that differently, I'm wondering if this metadata is truly like StaticResource or if it is just a one file metadata without folder to deploy.
Could you please give the content of your folder genAiPlannerBundle (tree **/genAiPlannerBundles) so I can understand better the structure on the file system ?