Closed joeyorlando closed 5 months ago
The current version of Grafana OnCall, at the time this issue was opened, is v1.5.1. If your issue pertains to an older version of Grafana OnCall, please be sure to list it in the PR description. Thank you :smile:!
This issue actually affects other the On-Call components (Schedule
, Route
, Integration
, Escalation
) which also need crossreference from other resources.
re-opened as we need to add selector and ref fields for a few more objects:
Integration
(check that there are no other related fields)Schedule
Route
Escalation
@MasterExecuson were they other objects you were using/came across that were missing selector/refs?
Once those changes are in, I'll go ahead and cut the v0.16.2 release over there
@joeyorlando , find bellow the link for the fields that are reference through ID and thus don't work great on Crossplane after this first commit.
Done.
I know it's actually as lot of field, but without those, creating a crossplane config for on call is very hard and requires a lot of custom mapping (speaking from expirience)...
What would you like to see!
Our Crossplane provider currently doesn't allow specifying a selector for an integration's default route's escalation chain (we only provide
defaultRoute.escalationChainId
). See our crossplane provider docs for more context.See
NotificationPolicy.contactPointRef
as an example of ideally how we should do this.Deliverables As a user of Crossplane whom is trying to code-ify my OnCall Integrations, I should be able to have my Integration's default route escalation chain reference an Escalation Chain
Product Area
Terraform
Anything else to add?
No response