MDE Module - Simplify entities parsing about sentinelautomationmodules HOT 4 CLOSED

@briandelmsft will do as soon as we pull the Enrich-Entity. Should we create a dependson in the ARM template or just rely on the users to add both?

from sentinelautomationmodules.

my thinking is that each module that calls enrich-entity will need a parameter for the enrich-entity resourceId, but not a 'dependancy' on. I don't think we can create a dependson unless it is fulfilled as part of the same deployment.

The main wrapper that deploys everything https://github.com/briandelmsft/SentinelAutomationModules/blob/main/Deploy/azuredeploy.json would deploy enrich-entity and it would have all the dependson statements that would ensure the resourceId of enrich-entities gets passed into each modules deployment parameters

from sentinelautomationmodules.

But we could make it a dependancy for the deployment, can't we? If it was already imported with the same version, then it will not reimport it (I think?). Or maybe the general strategy would be to deploy everything anyways.

from sentinelautomationmodules.

I think we would only ever deploy from the main deployment template so we would just need the parameter for the resourceId... If you did deploy a module directly then it would just be a matter of populating that string.

from sentinelautomationmodules.