drift-detection: custom digger plan workflow

[SalvoRusso8]

In the plan steps I have also infracost, so when the drift-detection action runs, also the infracost APIs are called, even if it’s useless for this job. Is it possible to split the workflow used by the drift-detection plan from the one used by a normal digger plan?