service can get out of sync

[kungfoome]

What happened?

State can get out of sync when manually doing operations to resources. In this particular case, if we create a service and attach it to an escalation policy, it doesn't check if the service has the right escalation policy assigned to it. We can manually assign the service a new escalation policy in PagerDuty directly and the k8s resource thinks that it's still in sync.

How can we reproduce it?

Create an escalation policy.
Create a service and attach that escalation policy
Assign a new escalation policy within Pagerduty manually on the newly created service

What environment did it happen in?

Crossplane version: latest
Provider version: 0.3.0