Parser's metadata deployment in error when parser already exist for another solution

[nlepagnez]

Describe the bug
We have 2 solutions that share multiple same parsers, but a customer can deploy one or the other so the 2 solutions need to deploy the shared parsers. Before Parsers are transformed as YAML objects, we didn't have any problem. Now when we do that we have a metadata conflict during the deployment.

How can we deploy the parser with the solutions without having error ?

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Microsoft Exchange Online Security Solution' in the Content Hub
2. Install the solution
3. Go to 'Microsoft Exchange On-Premises Security Solution' in the Content Hub
4. Install the solution

Expected behavior
Installation in success

Screenshots

[v-sudkharat]

Hi @nlepagnez, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates by 16-04-2024. Thanks!

[v-sudkharat]

Hey @nlepagnez, We are checking the issue cause for the deployment failure for Parser. Meanwhile, to get unblocked from this issue you can install the solution is another workspace where the solution is not already installed (Older versions).
This issue occurs only when updating the existing solution to new version.
Below sol. installed successfully in new workspace :-

Please let us know if you have any feedback on this.
Thanks!

[nlepagnez]

Hi @v-sudkharat. Exactly I was aware that it works on a new workspace, it's what we saw during our tests after we had this error. As we've just updated a major version of the solution, we're concerned about how customers will deploy it. I hope the cause can be found quickly.

Thank you.

[v-sudkharat]

@nlepagnez, Sure. we will definitely update you once we get cause or any other info from team. Thanks!

[v-sudkharat]

Hey @nlepagnez, Our team has found out the cause and fix for this issue, currently it is in testing. Team also made few modifications in solution packaging tool which is not merged yet. Once the updated packaging tool get merged into master. will update you. Thanks!

[nlepagnez]

IMPORTANT

Hi @v-sudkharat, I see a commit with an autopackage of the solutions : a31e95c

This brake totally the 2 Microsoft Exchange Security solutions as the Autopackage is not able to keep Default values or parser parameters. You need to stop the package deployment to the content hub and they need to correct :

• The CreateDefinitionUI with the modified text that is not correct
• The MainTemplate to reinsert parser parameters default values and texts.

[nlepagnez]

Hi @v-sudkharat, did the team finished to correct the error ? I see that the team repackaged the solutions, is now good ?

[v-sudkharat]

Hey @nlepagnez, still team is working on correction in packaging tool, and regarding publishing the solution there is still having same issue for parser metadata for which team is making changes.

[nlepagnez]

Hi @v-sudkharat, As I understand, the team pushed correction to packaging tool and also the solutions. Is it good now ? Is it possible to publish the new versions of the 2 solutions in the Content Hub ?

[v-sudkharat]

Hello @nlepagnez, Those solution is already pushed for get available in Content Hub from our end, and currently its pending with content hub team. We will ping you or share update with you over here once those solution is available in content hub with new versions.
Thanks!