List of triggers to start after deployment

[ChrisTeuben]

I miss the ability to specify per environment which triggers should be started automatically after a deployment.
It would be nice if this could be specified in a configuration file per environment.
This creates the possibility to create triggers to be enabled only in the target environment. In this way, the Azure DevOps CI / CD process can be performed without manual work afterwards.

[NowinskiK]

Chris, it IS possible to declare the desired state of trigger in the configuration file per environment.

[ChrisTeuben]

Oops, shame on me... I'll read the docs again with the right glasses on. :-)

[ChrisTeuben]

I still cannot find an example in the documentation but after some tries I got it working with this line in my config-Production.csv:
trigger,ProductionTrigger,runtimeState,"Started"

The trigger "ProductionTrigger", which is disabled on the source side, is now enabled on the target ("Production") side after a deployment.
I love it!

[NowinskiK]

I'm glad that this meets your expectation :)