Oooh dear. Could be great, could be disastrous.

Now IS the time!

Can I use that image to illustrate data quality issues…?

Lego Borg cube. Shut up and take ALL my money - resistance is, as we know, futile.

…that can (and will) change without notice.

If it does what it is supposed, a less elegant solution beats the solution that doesn't work 😜 It also means that I'm not completely off on a tangent if a pro suggests that solution (you're the second devops person to say the same thing).

Yes, but it feels overly complicated. As it stands, I have three different pipelines with different triggers that all run the same template with different parameters.

Thank you for offering :P The question I have is how to read which path triggered the pipeline run if I have a trigger like this:

trigger:
branches:
include:
- main
paths:
include:
- workspace/store-dev
- workspace/engineering-dev

The path should dictate actions later.

This. So much this.

...which can be said for most things, but I hear you (and agree). It is *a* tool, and it has its uses. It is not *the* tool, and it is absolutely not the tool it was sold as.

Sadly, yes. The emperor is buck naked, and nobody cares.

…yeah. Or I could learn on my own, and not have to deal with the bullshit in the first place. If it is supposed to make my life easier, it is failing. Miserably.

🤷 the code it produces for me ranges from flawed to completely syntactically incorrect. For me, it takes more time to deal worth the bullshit thank you actually read docs and learn how to do the thing in the first place.