Integration is the Schema for the Integrations API. Official documentation https://grafana.com/docs/oncall/latest/integrations/HTTP API https://grafana.com/docs/oncall/latest/oncall-api-reference/
Type
CRD
Group
oncall.grafana.crossplane.io
Version
v1alpha1
apiVersion: oncall.grafana.crossplane.io/v1alpha1
kind: Integration
IntegrationSpec defines the desired state of Integration
No description provided.
(Block List, Min: 1, Max: 1) The Default route for all alerts from the given integration (see below for nested schema) The Default route for all alerts from the given integration
(Block List, Max: 1) Jinja2 templates for Alert payload. An empty templates block will be ignored. (see below for nested schema) Jinja2 templates for Alert payload. An empty templates block will be ignored.
(Block List, Max: 1) Templates for Phone Call. (see below for nested schema) Templates for Phone Call.
(Block List, Max: 1) Templates for SMS. (see below for nested schema) Templates for SMS.
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
(Block List, Min: 1, Max: 1) The Default route for all alerts from the given integration (see below for nested schema) The Default route for all alerts from the given integration
(Block List, Max: 1) Jinja2 templates for Alert payload. An empty templates block will be ignored. (see below for nested schema) Jinja2 templates for Alert payload. An empty templates block will be ignored.
(Block List, Max: 1) Templates for Phone Call. (see below for nested schema) Templates for Phone Call.
(Block List, Max: 1) Templates for SMS. (see below for nested schema) Templates for SMS.
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
IntegrationStatus defines the observed state of Integration.
No description provided.
(Block List, Min: 1, Max: 1) The Default route for all alerts from the given integration (see below for nested schema) The Default route for all alerts from the given integration
(Block List, Max: 1) Jinja2 templates for Alert payload. An empty templates block will be ignored. (see below for nested schema) Jinja2 templates for Alert payload. An empty templates block will be ignored.
(Block List, Max: 1) Templates for Phone Call. (see below for nested schema) Templates for Phone Call.
(Block List, Max: 1) Templates for SMS. (see below for nested schema) Templates for SMS.
Conditions of the resource.
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.