Support for enabling/disabling azurerm_data_factory_trigger_schedule

markusgulden commented 3 years ago

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

At the moment, I can only create scheduled triggers using the azurerm_data_factory_trigger_schedule resource, but I am not able to activate them using Terraform (would have to use Portal or CLI for that instead). It would be great to be able to control this via a flag in the Terraform resource

New or Affected Resource(s)

azurerm_data_factory_trigger_schedule

Potential Terraform Configuration

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

References

https://docs.microsoft.com/en-us/azure/data-factory/how-to-create-schedule-trigger#azure-powershell

connor-miller-kr commented 3 years ago

Looking to bump this as I am running into the same issue/need. I unfortunately cannot update it through the portal as that requires rights at an RG level to publish changes to an ADF - something I do not have in my situation. At best, I have a Service Principal that should be able to run a local-exec or remote-exec command against it and am trying to work through a solution that way.

pvandenheede commented 2 years ago

This has been added in version azurerm_data_factory_trigger_schedule v2.77 https://github.com/hashicorp/terraform-provider-azurerm/blob/main/CHANGELOG-v2.md#2770-september-17-2021

antgustech commented 4 months ago

As I understood Azure documentation, you are supposed to stop triggers, deploy and then start triggers again after the deploy?

How is this handled with terraform? Should activated always be true and then we have to stop the triggers manually before we run terraform? Or should we ignore the activated field in TF and stop and start the triggers outside tf entirely?

hashicorp / terraform-provider-azurerm