Improved support for specifying time HH:MM in azurerm_automation_schedule

[Noel-Jones]

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

When specifying the start time you are required to enter an RFC format time or leave the time as null (in which case a time is generated 7 minutes in the future). I wish to schedule actions at a specific time each day. In Terraform it is nigh on impossible to create a time sting with a fixed time component that is at least 7 minutes in the future bearing in mind the start time may be the next day. Timestamp functions cannot be used because the resource would be recreated each execution. The time_static and time_offset resources allow a complex solution but still sub optimal solution to be devised. If there is anything better then I have not been able to work it out.

My request is that the start time field be allowed to specify only the time component, e.g. hh:mm:ss instead of a full time stamp. The next possible start time can be calculated ensuring that it is 7 minutes in the future.

New or Affected Resource(s)

• azurerm_automation_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

• #0000

[MattGarner-N]

Use timestamp and just do this?

lifecycle {
ignore_changes = [
start_time
]
}