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

provider/pagerduty: missing key for weekly layer restriction #10033

Closed
blalor opened this issue Nov 11, 2016 · 3 comments · Fixed by #10069
Closed

provider/pagerduty: missing key for weekly layer restriction #10033

blalor opened this issue Nov 11, 2016 · 3 comments · Fixed by #10069

Comments

@blalor
Copy link
Contributor

blalor commented Nov 11, 2016

Terraform Version

Terraform v0.7.10

Affected Resource(s)

  • pagerduty_schedule

Terraform Configuration Files

resource "pagerduty_schedule" "PlatformTest" {
    name = "Platform Test"
    time_zone = "America/New_York"
    description = "testing some terraformy stuff"
    
    ## Monday 9am to Wednesday 5pm
    layer {
        name = "M9a-W5p"
        start = "2016-11-13T23:00:00Z"
        rotation_virtual_start = "2016-11-09T23:00:00Z"

        rotation_turn_length_seconds = "${ 7 * 24 * 3600 }" ## 7 days

        restriction {
            type = "weekly_restriction"
            start_time_of_day = "09:00:00"
            start_day_of_week = 1
            duration_seconds = "${ 56 * 3600 }" ## 56 hours
        }
        
        users = [ "PDYDMY2" ]
    }
}

Debug Output

Expected Behavior

Should have been able to create schedule layer with a weekly_restriction restriction that specifies the starting day of the week.

Actual Behavior

When not including the start_day_of_week attribute, terraform apply gets an error from the PagerDuty API because that attribute is required. When specifying the attribute in the Terraform config, terraform apply fails because the attribute is unknown to the provider.

@heimweh
Copy link
Contributor

heimweh commented Nov 12, 2016

Hi @blalor, thank you so much for this bug report. I'm currently looking into this.
This seems to be tracing back to the client library we're using which doesn't yet support the attribute start_day_of_week. I have a pending PR in the client library waiting and as soon that one's been merged I'll look into fixing the resource.

Really sorry about this and I'm hoping to get this resolved quickly.

@blalor
Copy link
Contributor Author

blalor commented Nov 12, 2016

Thank you @heimweh!

@ghost
Copy link

ghost commented Apr 18, 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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants