kevinwedwards

This is affecting us as well.

@hectorhdzg Is this still outstanding? I've got a similar issue: nextjs app (client + app-api) .net core internal APIs nextjs client nextJs serverside code .NET Core APIs I get AppInsights...

@hectorhdzg If I understand correctly cross-fetch *should* provide a node-fetch impl vs 'native fetch' [cross-fetch](https://github.com/lquixada/cross-fetch) Essentially nextjs 'client' (using applicationinsights-web sdk) page, makes a request to a node.js (running applicationinsights-node),...

adding to schedule block: depends_on = [ pagerduty_team.team1, pagerduty_team.team2 ] Identical Result: # pagerduty_schedule.pd_schedudule will be updated in-place ~ resource "pagerduty_schedule" "pd_schedudule" { id = "P2W357J" name = "ScheduleName" ~...

I've 100% confirmed the issue is the way the GET call to the TF API is returning 'sorted' values. previously we had two instances. one worked and one didn't. We...

Sort() didn't fix it. This needs to be fixed. # pagerduty_schedule.pd_sched_escalation will be updated in-place ``` ~ resource "pagerduty_schedule" "pd_sched_escalation" { id = "P1W1DX3" name = "Escalation" ~ teams =...

This is impacting us as well; shouldn't be marked as stale.