Destination is the Schema for the Destinations API. Create and manage a notification destination for notifications in New Relic.
Type
CRD
Group
alert.newrelic.upbound.io
Version
v1alpha1
apiVersion: alert.newrelic.upbound.io/v1alpha1
kind: Destination
DestinationSpec defines the desired state of Destination
No description provided.
A nested block that describes a basic username and password authentication credentials. Only one auth_basic block is permitted per notification destination definition. See Nested auth_basic blocks below for details. Basic username and password authentication credentials.
A nested block that describes a custom header authentication credentials. Multiple blocks are permitted per notification destination definition. Nested auth_custom_header blocks below for details. Custom header based authentication
A nested block that describes a token authentication credentials. Only one auth_token block is permitted per notification destination definition. See Nested auth_token blocks below for details. Token authentication credentials.
A nested block that describes a notification destination property. See Nested property blocks below for details. Notification destination property type.
A nested block that describes a URL that contains sensitive data at the path or parameters. Only one secure_url block is permitted per notification destination definition. See Nested secure_url blocks below for details. URL in secure format
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.
A nested block that describes a basic username and password authentication credentials. Only one auth_basic block is permitted per notification destination definition. See Nested auth_basic blocks below for details. Basic username and password authentication credentials.
A nested block that describes a custom header authentication credentials. Multiple blocks are permitted per notification destination definition. Nested auth_custom_header blocks below for details. Custom header based authentication
A nested block that describes a token authentication credentials. Only one auth_token block is permitted per notification destination definition. See Nested auth_token blocks below for details. Token authentication credentials.
A nested block that describes a notification destination property. See Nested property blocks below for details. Notification destination property type.
A nested block that describes a URL that contains sensitive data at the path or parameters. Only one secure_url block is permitted per notification destination definition. See Nested secure_url blocks below for details. URL in secure format
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.
DestinationStatus defines the observed state of Destination.
No description provided.
A nested block that describes a basic username and password authentication credentials. Only one auth_basic block is permitted per notification destination definition. See Nested auth_basic blocks below for details. Basic username and password authentication credentials.
A nested block that describes a custom header authentication credentials. Multiple blocks are permitted per notification destination definition. Nested auth_custom_header blocks below for details. Custom header based authentication
A nested block that describes a token authentication credentials. Only one auth_token block is permitted per notification destination definition. See Nested auth_token blocks below for details. Token authentication credentials.
A nested block that describes a notification destination property. See Nested property blocks below for details. Notification destination property type.
A nested block that describes a URL that contains sensitive data at the path or parameters. Only one secure_url block is permitted per notification destination definition. See Nested secure_url blocks below for details. URL in secure format
Conditions of the resource.
foo
apiVersion: alert.newrelic.upbound.io/v1alpha1
kind: Destination
metadata:
annotations:
meta.upbound.io/example-id: alert/v1alpha1/destination
labels:
testing.upbound.io/example-name: example-destination
name: foo
spec:
forProvider:
name: email-example
property:
- key: email
value: email@email.com,email2@email.com
type: EMAIL
© 2024 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.