Contact Details [Optional]

No response

Feature Description

As of today (25th June 25), to get a step to use a step operator, we have to specify the step operator name as parameter (either in the yaml or in the decorator parameter)

I'd like the ability to specify as parameter use_step_operator: True so that whatever the stack is it uses the only one step operator used.

Problem or Use Case

Having to specify the step operator name makes the runs less platform/stack agnostic. step operator tend to have names tied to their resources ex: gcp-e2-standard-16
it means that if we do not have the same step operator name within a different stack we can't switch without modifying the code/configuration

Proposed Solution

As of now, there is no way to add more than one step operator we could fallback on the only one step operator available.

Alternatives Considered

No response

Additional Context

No response

Priority

Medium - Would improve my workflow

Code of Conduct

• I agree to follow this project's Code of Conduct