Docs Packages
  1. Packages
  2. Dynatrace
  3. API Docs
  4. AnsibleTowerNotification
Dynatrace v0.1.0 published on Wednesday, May 24, 2023 by Lbrlabs
lbrlabs/pulumi-dynatrace

dynatrace.AnsibleTowerNotification

Explore with Pulumi AI

dynatrace logo
Dynatrace v0.1.0 published on Wednesday, May 24, 2023 by Lbrlabs
lbrlabs/pulumi-dynatrace

    Create AnsibleTowerNotification Resource

    new AnsibleTowerNotification(name: string, args: AnsibleTowerNotificationArgs, opts?: CustomResourceOptions);
    @overload
def AnsibleTowerNotification(resource_name: str,
                             opts: Optional[ResourceOptions] = None,
                             active: Optional[bool] = None,
                             custom_message: Optional[str] = None,
                             insecure: Optional[bool] = None,
                             job_template_url: Optional[str] = None,
                             legacy_id: Optional[str] = None,
                             name: Optional[str] = None,
                             password: Optional[str] = None,
                             profile: Optional[str] = None,
                             username: Optional[str] = None)
@overload
def AnsibleTowerNotification(resource_name: str,
                             args: AnsibleTowerNotificationArgs,
                             opts: Optional[ResourceOptions] = None)
    func NewAnsibleTowerNotification(ctx *Context, name string, args AnsibleTowerNotificationArgs, opts ...ResourceOption) (*AnsibleTowerNotification, error)
    public AnsibleTowerNotification(string name, AnsibleTowerNotificationArgs args, CustomResourceOptions? opts = null)
    public AnsibleTowerNotification(String name, AnsibleTowerNotificationArgs args)
public AnsibleTowerNotification(String name, AnsibleTowerNotificationArgs args, CustomResourceOptions options)

    type: dynatrace:AnsibleTowerNotification
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
    name string
    The unique name of the resource.
    args AnsibleTowerNotificationArgs
    The arguments to resource properties.
    opts CustomResourceOptions
    Bag of options to control resource's behavior.
    resource_name str
    The unique name of the resource.
    args AnsibleTowerNotificationArgs
    The arguments to resource properties.
    opts ResourceOptions
    Bag of options to control resource's behavior.
    ctx Context
    Context object for the current deployment.
    name string
    The unique name of the resource.
    args AnsibleTowerNotificationArgs
    The arguments to resource properties.
    opts ResourceOption
    Bag of options to control resource's behavior.
    name string
    The unique name of the resource.
    args AnsibleTowerNotificationArgs
    The arguments to resource properties.
    opts CustomResourceOptions
    Bag of options to control resource's behavior.
    name String
    The unique name of the resource.
    args AnsibleTowerNotificationArgs
    The arguments to resource properties.
    options CustomResourceOptions
    Bag of options to control resource's behavior.

    AnsibleTowerNotification Resource Properties

    To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.

    Inputs

    The AnsibleTowerNotification resource accepts the following input properties:

    CustomMessage string

    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 of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level 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

    JobTemplateUrl string

    The URL of the target Ansible Tower job template

    Profile string

    The ID of the associated alerting profile.

    Username string

    The username of the Ansible Tower account

    Active bool

    The notification is active (true) or inactive (false). Default is false.

    Insecure bool

    Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates. Default is false.

    LegacyId string

    The ID of these settings when referred to from resources requiring the REST API V1 keys

    Name string

    The display name within the Dynatrace WebUI.

    Password string

    The password for the Ansible Tower account

    CustomMessage string

    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 of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level 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

    JobTemplateUrl string

    The URL of the target Ansible Tower job template

    Profile string

    The ID of the associated alerting profile.

    Username string

    The username of the Ansible Tower account

    Active bool

    The notification is active (true) or inactive (false). Default is false.

    Insecure bool

    Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates. Default is false.

    LegacyId string

    The ID of these settings when referred to from resources requiring the REST API V1 keys

    Name string

    The display name within the Dynatrace WebUI.

    Password string

    The password for the Ansible Tower account

    customMessage String

    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 of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level 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

    jobTemplateUrl String

    The URL of the target Ansible Tower job template

    profile String

    The ID of the associated alerting profile.

    username String

    The username of the Ansible Tower account

    active Boolean

    The notification is active (true) or inactive (false). Default is false.

    insecure Boolean

    Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates. Default is false.

    legacyId String

    The ID of these settings when referred to from resources requiring the REST API V1 keys

    name String

    The display name within the Dynatrace WebUI.

    password String

    The password for the Ansible Tower account

    customMessage string

    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 of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level 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

    jobTemplateUrl string

    The URL of the target Ansible Tower job template

    profile string

    The ID of the associated alerting profile.

    username string

    The username of the Ansible Tower account

    active boolean

    The notification is active (true) or inactive (false). Default is false.

    insecure boolean

    Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates. Default is false.

    legacyId string

    The ID of these settings when referred to from resources requiring the REST API V1 keys

    name string

    The display name within the Dynatrace WebUI.

    password string

    The password for the Ansible Tower account

    custom_message str

    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 of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level 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

    job_template_url str

    The URL of the target Ansible Tower job template

    profile str

    The ID of the associated alerting profile.

    username str

    The username of the Ansible Tower account

    active bool

    The notification is active (true) or inactive (false). Default is false.

    insecure bool

    Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates. Default is false.

    legacy_id str

    The ID of these settings when referred to from resources requiring the REST API V1 keys

    name str

    The display name within the Dynatrace WebUI.

    password str

    The password for the Ansible Tower account

    customMessage String

    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 of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level 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

    jobTemplateUrl String

    The URL of the target Ansible Tower job template

    profile String

    The ID of the associated alerting profile.

    username String

    The username of the Ansible Tower account

    active Boolean

    The notification is active (true) or inactive (false). Default is false.

    insecure Boolean

    Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates. Default is false.

    legacyId String

    The ID of these settings when referred to from resources requiring the REST API V1 keys

    name String

    The display name within the Dynatrace WebUI.

    password String

    The password for the Ansible Tower account

    Outputs

    All input properties are implicitly available as output properties. Additionally, the AnsibleTowerNotification resource produces the following output properties:

    Id string

    The provider-assigned unique ID for this managed resource.

    Id string

    The provider-assigned unique ID for this managed resource.

    id String

    The provider-assigned unique ID for this managed resource.

    id string

    The provider-assigned unique ID for this managed resource.

    id str

    The provider-assigned unique ID for this managed resource.

    id String

    The provider-assigned unique ID for this managed resource.

    Look up Existing AnsibleTowerNotification Resource

    Get an existing AnsibleTowerNotification resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.

    public static get(name: string, id: Input<ID>, state?: AnsibleTowerNotificationState, opts?: CustomResourceOptions): AnsibleTowerNotification
    @staticmethod
def get(resource_name: str,
        id: str,
        opts: Optional[ResourceOptions] = None,
        active: Optional[bool] = None,
        custom_message: Optional[str] = None,
        insecure: Optional[bool] = None,
        job_template_url: Optional[str] = None,
        legacy_id: Optional[str] = None,
        name: Optional[str] = None,
        password: Optional[str] = None,
        profile: Optional[str] = None,
        username: Optional[str] = None) -> AnsibleTowerNotification
    func GetAnsibleTowerNotification(ctx *Context, name string, id IDInput, state *AnsibleTowerNotificationState, opts ...ResourceOption) (*AnsibleTowerNotification, error)
    public static AnsibleTowerNotification Get(string name, Input<string> id, AnsibleTowerNotificationState? state, CustomResourceOptions? opts = null)
    public static AnsibleTowerNotification get(String name, Output<String> id, AnsibleTowerNotificationState state, CustomResourceOptions options)
    Resource lookup is not supported in YAML
    name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    state
    Any extra arguments used during the lookup.
    opts
    A bag of options that control this resource's behavior.
    resource_name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    state
    Any extra arguments used during the lookup.
    opts
    A bag of options that control this resource's behavior.
    name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    state
    Any extra arguments used during the lookup.
    opts
    A bag of options that control this resource's behavior.
    name
    The unique name of the resulting resource.
    id
    The unique provider ID of the resource to lookup.
    state
    Any extra arguments used during the lookup.
    opts
    A bag of options that control this resource's behavior.
    The following state arguments are supported:
    Active bool

    The notification is active (true) or inactive (false). Default is false.

    CustomMessage string

    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 of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level 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

    Insecure bool

    Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates. Default is false.

    JobTemplateUrl string

    The URL of the target Ansible Tower job template

    LegacyId string

    The ID of these settings when referred to from resources requiring the REST API V1 keys

    Name string

    The display name within the Dynatrace WebUI.

    Password string

    The password for the Ansible Tower account

    Profile string

    The ID of the associated alerting profile.

    Username string

    The username of the Ansible Tower account

    Active bool

    The notification is active (true) or inactive (false). Default is false.

    CustomMessage string

    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 of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level 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

    Insecure bool

    Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates. Default is false.

    JobTemplateUrl string

    The URL of the target Ansible Tower job template

    LegacyId string

    The ID of these settings when referred to from resources requiring the REST API V1 keys

    Name string

    The display name within the Dynatrace WebUI.

    Password string

    The password for the Ansible Tower account

    Profile string

    The ID of the associated alerting profile.

    Username string

    The username of the Ansible Tower account

    active Boolean

    The notification is active (true) or inactive (false). Default is false.

    customMessage String

    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 of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level 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

    insecure Boolean

    Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates. Default is false.

    jobTemplateUrl String

    The URL of the target Ansible Tower job template

    legacyId String

    The ID of these settings when referred to from resources requiring the REST API V1 keys

    name String

    The display name within the Dynatrace WebUI.

    password String

    The password for the Ansible Tower account

    profile String

    The ID of the associated alerting profile.

    username String

    The username of the Ansible Tower account

    active boolean

    The notification is active (true) or inactive (false). Default is false.

    customMessage string

    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 of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level 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

    insecure boolean

    Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates. Default is false.

    jobTemplateUrl string

    The URL of the target Ansible Tower job template

    legacyId string

    The ID of these settings when referred to from resources requiring the REST API V1 keys

    name string

    The display name within the Dynatrace WebUI.

    password string

    The password for the Ansible Tower account

    profile string

    The ID of the associated alerting profile.

    username string

    The username of the Ansible Tower account

    active bool

    The notification is active (true) or inactive (false). Default is false.

    custom_message str

    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 of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level 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

    insecure bool

    Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates. Default is false.

    job_template_url str

    The URL of the target Ansible Tower job template

    legacy_id str

    The ID of these settings when referred to from resources requiring the REST API V1 keys

    name str

    The display name within the Dynatrace WebUI.

    password str

    The password for the Ansible Tower account

    profile str

    The ID of the associated alerting profile.

    username str

    The username of the Ansible Tower account

    active Boolean

    The notification is active (true) or inactive (false). Default is false.

    customMessage String

    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 of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE. * {ProblemSeverity}: The severity level 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

    insecure Boolean

    Accept any, including self-signed and invalid, SSL certificate (true) or only trusted (false) certificates. Default is false.

    jobTemplateUrl String

    The URL of the target Ansible Tower job template

    legacyId String

    The ID of these settings when referred to from resources requiring the REST API V1 keys

    name String

    The display name within the Dynatrace WebUI.

    password String

    The password for the Ansible Tower account

    profile String

    The ID of the associated alerting profile.

    username String

    The username of the Ansible Tower account

    Package Details

    Repository
    dynatrace lbrlabs/pulumi-dynatrace
    License
    Apache-2.0
    Notes

    This Pulumi package is based on the dynatrace Terraform Provider.

    dynatrace logo
    Dynatrace v0.1.0 published on Wednesday, May 24, 2023 by Lbrlabs
    lbrlabs/pulumi-dynatrace