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

azurerm_automation_schedule fails when recurring. Interval options missing/non-importable #463

Closed
draggeta opened this issue Oct 27, 2017 · 2 comments · Fixed by #1384
Closed
Assignees
Milestone

Comments

@draggeta
Copy link
Contributor

Terraform Version

0.10.8

Affected Resource(s)

  • azurerm_automation_schedule

Terraform Configuration Files

resource "azurerm_automation_schedule" "schedule_prd_tas_admin_sync" {
  name                = "ProductionTOPdeskAdministratorsSync"
  resource_group_name = "${azurerm_automation_account.automation.resource_group_name}"
  account_name        = "${azurerm_automation_account.automation.name}"
  frequency           = "Hour"
  timezone            = "W. Europe Standard Time"
  start_time          = "2017-10-28T02:07:00+01:00"
  description         = "Automation schedule to start the synchronization of admin accounts to TAS servers."
}

Debug Output

https://gist.github.com/draggeta/8af664cd5858f5093c982763e4f2bd27

Expected Behavior

When reading/creating a recurring schedule , this should not fail. Also there are missing options such as days of week, weeks of months etc.

Actual Behavior

Any time you try to perform a CRUD operation on a recurring schedule, you get an error regarding the frequency interval. This seems to be caused by the fact that it is an integer and json cannot unmarshal it to a string. Sadly, that is as far as my Go knowledge goes.

Steps to Reproduce

Happens on the following:

  1. terraform apply
  2. terraform plan
  3. terraform import

Important Factoids

Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs?

References

@achandmsft achandmsft added this to the Future milestone Mar 10, 2018
@katbyte katbyte self-assigned this May 13, 2018
@katbyte katbyte modified the milestones: Future, 1.6.0 May 13, 2018
@tombuildsstuff tombuildsstuff modified the milestones: 1.6.0, 1.7.0 May 21, 2018
katbyte added a commit that referenced this issue Jun 15, 2018
…le_interval Fixes #463 & #1127.

Various improvements to automation account & schedule (interval property for recurring). Fixes #463 & #1127.
@katbyte
Copy link
Collaborator

katbyte commented Jun 16, 2018

Hey @draggeta,

A fix to allow add the interval property and allow recurring schedules was released today as part of 1.7!

@ghost
Copy link

ghost commented Mar 30, 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 and limited conversation to collaborators Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
5 participants