import * as pulumi from "@pulumi/pulumi"; export declare class AnsibleTowerNotification extends pulumi.CustomResource { /** * Get an existing AnsibleTowerNotification resource's state with the given name, ID, and optional extra * properties used to qualify the lookup. * * @param name The _unique_ name of the resulting resource. * @param id The _unique_ provider ID of the resource to lookup. * @param state Any extra arguments used during the lookup. * @param opts Optional settings to control the behavior of the CustomResource. */ static get(name: string, id: pulumi.Input, state?: AnsibleTowerNotificationState, opts?: pulumi.CustomResourceOptions): AnsibleTowerNotification; /** * Returns true if the given object is an instance of AnsibleTowerNotification. This is designed to work even * when multiple copies of the Pulumi SDK have been loaded into the same process. */ static isInstance(obj: any): obj is AnsibleTowerNotification; /** * The notification is active (`true`) or inactive (`false`). Default is `false`. */ readonly active: pulumi.Output; /** * The custom message of the notification. This message will be displayed in the extra variables **Message** field of your job template. You can use the following placeholders: * `{ImpactedEntities}`: Details about the entities impacted by the problem in form of a JSON array. * `{ImpactedEntity}`: The entity impacted by the problem or *X* impacted entities. * `{PID}`: The ID of the reported problem. * `{ProblemDetailsText}`: All problem event details, including root cause, as a text-formatted string. * `{ProblemID}`: The display number of the reported problem. * `{ProblemImpact}`: The [impact level](https://www.dynatrace.com/support/help/shortlink/impact-analysis) of the problem. Possible values are `APPLICATION`, `SERVICE`, and `INFRASTRUCTURE`. * `{ProblemSeverity}`: The [severity level](https://www.dynatrace.com/support/help/shortlink/event-types) of the problem. Possible values are `AVAILABILITY`, `ERROR`, `PERFORMANCE`, `RESOURCE_CONTENTION`, and `CUSTOM_ALERT`. * `{ProblemTitle}`: A short description of the problem. * `{ProblemURL}`: The URL of the problem within Dynatrace. * `{State}`: The state of the problem. Possible values are `OPEN` and `RESOLVED`. * `{Tags}`: The list of tags that are defined for all impacted entities, separated by commas */ readonly customMessage: pulumi.Output; /** * Accept any, including self-signed and invalid, SSL certificate (`true`) or only trusted (`false`) certificates. Default is `false`. */ readonly insecure: pulumi.Output; /** * The URL of the target Ansible Tower job template */ readonly jobTemplateUrl: pulumi.Output; /** * The ID of these settings when referred to from resources requiring the REST API V1 keys */ readonly legacyId: pulumi.Output; /** * The display name within the Dynatrace WebUI. */ readonly name: pulumi.Output; /** * The password for the Ansible Tower account */ readonly password: pulumi.Output; /** * The ID of the associated alerting profile. */ readonly profile: pulumi.Output; /** * The username of the Ansible Tower account */ readonly username: pulumi.Output; /** * Create a AnsibleTowerNotification resource with the given unique name, arguments, and options. * * @param name The _unique_ name of the resource. * @param args The arguments to use to populate this resource's properties. * @param opts A bag of options that control this resource's behavior. */ constructor(name: string, args: AnsibleTowerNotificationArgs, opts?: pulumi.CustomResourceOptions); } /** * Input properties used for looking up and filtering AnsibleTowerNotification resources. */ export interface AnsibleTowerNotificationState { /** * The notification is active (`true`) or inactive (`false`). Default is `false`. */ active?: pulumi.Input; /** * The custom message of the notification. This message will be displayed in the extra variables **Message** field of your job template. You can use the following placeholders: * `{ImpactedEntities}`: Details about the entities impacted by the problem in form of a JSON array. * `{ImpactedEntity}`: The entity impacted by the problem or *X* impacted entities. * `{PID}`: The ID of the reported problem. * `{ProblemDetailsText}`: All problem event details, including root cause, as a text-formatted string. * `{ProblemID}`: The display number of the reported problem. * `{ProblemImpact}`: The [impact level](https://www.dynatrace.com/support/help/shortlink/impact-analysis) of the problem. Possible values are `APPLICATION`, `SERVICE`, and `INFRASTRUCTURE`. * `{ProblemSeverity}`: The [severity level](https://www.dynatrace.com/support/help/shortlink/event-types) of the problem. Possible values are `AVAILABILITY`, `ERROR`, `PERFORMANCE`, `RESOURCE_CONTENTION`, and `CUSTOM_ALERT`. * `{ProblemTitle}`: A short description of the problem. * `{ProblemURL}`: The URL of the problem within Dynatrace. * `{State}`: The state of the problem. Possible values are `OPEN` and `RESOLVED`. * `{Tags}`: The list of tags that are defined for all impacted entities, separated by commas */ customMessage?: pulumi.Input; /** * Accept any, including self-signed and invalid, SSL certificate (`true`) or only trusted (`false`) certificates. Default is `false`. */ insecure?: pulumi.Input; /** * The URL of the target Ansible Tower job template */ jobTemplateUrl?: pulumi.Input; /** * The ID of these settings when referred to from resources requiring the REST API V1 keys */ legacyId?: pulumi.Input; /** * The display name within the Dynatrace WebUI. */ name?: pulumi.Input; /** * The password for the Ansible Tower account */ password?: pulumi.Input; /** * The ID of the associated alerting profile. */ profile?: pulumi.Input; /** * The username of the Ansible Tower account */ username?: pulumi.Input; } /** * The set of arguments for constructing a AnsibleTowerNotification resource. */ export interface AnsibleTowerNotificationArgs { /** * The notification is active (`true`) or inactive (`false`). Default is `false`. */ active?: pulumi.Input; /** * The custom message of the notification. This message will be displayed in the extra variables **Message** field of your job template. You can use the following placeholders: * `{ImpactedEntities}`: Details about the entities impacted by the problem in form of a JSON array. * `{ImpactedEntity}`: The entity impacted by the problem or *X* impacted entities. * `{PID}`: The ID of the reported problem. * `{ProblemDetailsText}`: All problem event details, including root cause, as a text-formatted string. * `{ProblemID}`: The display number of the reported problem. * `{ProblemImpact}`: The [impact level](https://www.dynatrace.com/support/help/shortlink/impact-analysis) of the problem. Possible values are `APPLICATION`, `SERVICE`, and `INFRASTRUCTURE`. * `{ProblemSeverity}`: The [severity level](https://www.dynatrace.com/support/help/shortlink/event-types) of the problem. Possible values are `AVAILABILITY`, `ERROR`, `PERFORMANCE`, `RESOURCE_CONTENTION`, and `CUSTOM_ALERT`. * `{ProblemTitle}`: A short description of the problem. * `{ProblemURL}`: The URL of the problem within Dynatrace. * `{State}`: The state of the problem. Possible values are `OPEN` and `RESOLVED`. * `{Tags}`: The list of tags that are defined for all impacted entities, separated by commas */ customMessage: pulumi.Input; /** * Accept any, including self-signed and invalid, SSL certificate (`true`) or only trusted (`false`) certificates. Default is `false`. */ insecure?: pulumi.Input; /** * The URL of the target Ansible Tower job template */ jobTemplateUrl: pulumi.Input; /** * The ID of these settings when referred to from resources requiring the REST API V1 keys */ legacyId?: pulumi.Input; /** * The display name within the Dynatrace WebUI. */ name?: pulumi.Input; /** * The password for the Ansible Tower account */ password?: pulumi.Input; /** * The ID of the associated alerting profile. */ profile: pulumi.Input; /** * The username of the Ansible Tower account */ username: pulumi.Input; }