-
Notifications
You must be signed in to change notification settings - Fork 2
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
Diff shown on pagerduty.Service
without code changes
#624
Labels
awaiting-upstream
The issue cannot be resolved without action in another repository (may be owned by Pulumi).
blocked
The issue cannot be resolved without 3rd party action.
kind/bug
Some behavior is incorrect or out of spec
Comments
ringods
added
kind/bug
Some behavior is incorrect or out of spec
needs-triage
Needs attention from the triage team
labels
Oct 1, 2024
Thanks for reporting. I could repro the issue with the provided code. This might be a problem with the provider: {
"method": "/pulumirpc.ResourceProvider/Diff",
"request": {
"id": "P9Y95XU",
"urn": "urn:pulumi:dev::pagerduty_624::pagerduty:index/service:Service::dummy-service",
"olds": {
"acknowledgementTimeout": "1800",
"alertCreation": "create_alerts_and_incidents",
"alertGrouping": null,
"alertGroupingParameters": null,
"alertGroupingTimeout": "null",
"autoPauseNotificationsParameters": {
"enabled": true,
"timeout": 300
},
"autoResolveTimeout": "null",
"createdAt": "2024-10-01T12:11:11+01:00",
"description": "PagerDuty service for My Dummy service",
"escalationPolicy": "PCX4X0Q",
"htmlUrl": "https://pulumibot.pagerduty.com/service-directory/P9Y95XU",
"id": "P9Y95XU",
"incidentUrgencyRule": {
"duringSupportHours": null,
"outsideSupportHours": null,
"type": "constant",
"urgency": "low"
},
"lastIncidentTimestamp": "",
"name": "MyDummy",
"responsePlay": null,
"scheduledActions": [],
"status": "active",
"supportHours": null,
"type": "service"
},
"news": {
"__defaults": [
"acknowledgementTimeout"
],
"acknowledgementTimeout": "1800",
"autoPauseNotificationsParameters": {
"__defaults": [],
"enabled": true,
"timeout": 300
},
"autoResolveTimeout": "null",
"description": "PagerDuty service for My Dummy service",
"escalationPolicy": "PCX4X0Q",
"incidentUrgencyRule": {
"__defaults": [],
"duringSupportHours": {
"__defaults": [],
"type": "constant",
"urgency": "low"
},
"outsideSupportHours": {
"__defaults": [],
"type": "constant",
"urgency": "low"
},
"type": "constant",
"urgency": "low"
},
"name": "MyDummy"
},
"oldInputs": {
"__defaults": [
"acknowledgementTimeout"
],
"acknowledgementTimeout": "1800",
"autoPauseNotificationsParameters": {
"__defaults": [],
"enabled": true,
"timeout": 300
},
"autoResolveTimeout": "null",
"description": "PagerDuty service for My Dummy service",
"escalationPolicy": "PCX4X0Q",
"incidentUrgencyRule": {
"__defaults": [],
"duringSupportHours": {
"__defaults": [],
"type": "constant",
"urgency": "low"
},
"outsideSupportHours": {
"__defaults": [],
"type": "constant",
"urgency": "low"
},
"type": "constant",
"urgency": "low"
},
"name": "MyDummy"
},
"name": "dummy-service",
"type": "pagerduty:index/service:Service"
},
"response": {
"changes": "DIFF_SOME",
"diffs": [
"incidentUrgencyRule"
],
"detailedDiff": {
"incidentUrgencyRule.duringSupportHours": {
"kind": "UPDATE"
},
"incidentUrgencyRule.duringSupportHours.type": {},
"incidentUrgencyRule.duringSupportHours.urgency": {},
"incidentUrgencyRule.outsideSupportHours": {
"kind": "UPDATE"
},
"incidentUrgencyRule.outsideSupportHours.type": {},
"incidentUrgencyRule.outsideSupportHours.urgency": {}
},
"hasDetailedDiff": true
},
"metadata": {
"kind": "resource",
"mode": "client",
"name": "pagerduty"
}
} The incidentUrgencyRules are not saved in the state and we correctly recognize a diff when previewing. I'll try to repro in TF. |
Yeah, same thing in terraform: terraform {
required_providers {
pagerduty = {
source = "pagerduty/pagerduty"
version = ">= 2.2.1"
}
}
}
resource "pagerduty_user" "test_user" {
name = "Earline Greenholt"
email = "<EMAIL>"
}
resource "pagerduty_escalation_policy" "escalate_via_email" {
name = "Engineering Escalation Policy"
num_loops = 2
rule {
escalation_delay_in_minutes = 10
target {
type = "user_reference"
id = pagerduty_user.test_user.id
}
}
}
resource "pagerduty_service" "dummy_service" {
name = "MyDummy"
description = "PagerDuty service for My Dummy service"
escalation_policy = pagerduty_escalation_policy.escalate_via_email.id
auto_pause_notifications_parameters {
enabled = true
timeout = 300
}
auto_resolve_timeout = null
incident_urgency_rule {
type = "constant"
during_support_hours {
type = "constant"
urgency = "low"
}
outside_support_hours {
type = "constant"
urgency = "low"
}
urgency = "low"
}
}
|
opened PagerDuty/terraform-provider-pagerduty#933 upstream |
VenelinMartinov
added
awaiting-upstream
The issue cannot be resolved without action in another repository (may be owned by Pulumi).
blocked
The issue cannot be resolved without 3rd party action.
labels
Oct 1, 2024
As a workaround does |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
awaiting-upstream
The issue cannot be resolved without action in another repository (may be owned by Pulumi).
blocked
The issue cannot be resolved without 3rd party action.
kind/bug
Some behavior is incorrect or out of spec
Describe what happened
pulumi up
to apply itpulumi up
a second time without make any code changesYou will notice the following diff being proposed on the second
up
run:A
pulumi refresh
proposes the following diff:Sample program
Replace the
<email>
placeholder in thepagerduty.User
resource when using this program to test.Log output
No response
Affected Resource(s)
pagerduty.Service
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: