Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for startTime and timeZone in azurerm_logic_app_trigger_recurrence #4316

Closed
Leon99 opened this issue Sep 13, 2019 · 2 comments · Fixed by #8829
Closed

Support for startTime and timeZone in azurerm_logic_app_trigger_recurrence #4316

Leon99 opened this issue Sep 13, 2019 · 2 comments · Fixed by #8829

Comments

@Leon99
Copy link

Leon99 commented Sep 13, 2019

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

In the light of the Azure Scheduler retirement and migration to Logic Apps, it would be great to have support for startTime (more importantly) and timeZone (not that important, but why not).

New or Affected Resource(s)

  • azurerm_logic_app_trigger_recurrence

Potential Terraform Configuration

resource "azurerm_logic_app_trigger_recurrence" "test" {
  name         = "run-every-day"
  logic_app_id = "${azurerm_logic_app_workflow.test.id}"
  frequency    = "Day"
  interval     = 1
  start_time   = "..."
  time_zone    = "..."
}
@ghost
Copy link

ghost commented Oct 29, 2020

This has been released in version 2.34.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.34.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented Nov 29, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Nov 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants