pulumi-splunk 1.3.0a1756363339__tar.gz → 1.3.0a1756506919__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Potentially problematic release.
This version of pulumi-splunk might be problematic. Click here for more details.
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/PKG-INFO +1 -1
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/config/__init__.pyi +1 -2
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/config/vars.py +1 -2
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/provider.py +4 -8
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/pulumi-plugin.json +1 -1
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/saved_searches.py +28 -98
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk.egg-info/PKG-INFO +1 -1
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pyproject.toml +1 -1
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/README.md +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/__init__.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/_inputs.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/_utilities.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/admin_saml_groups.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/apps_local.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/authentication_users.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/authorization_roles.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/config/__init__.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/configs_conf.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/data_ui_views.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/generic_acl.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/global_http_event_collector.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/indexes.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/inputs_http_event_collector.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/inputs_monitor.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/inputs_script.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/inputs_tcp_cooked.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/inputs_tcp_raw.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/inputs_tcp_splunk_tcp_token.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/inputs_tcp_ssl.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/inputs_udp.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/lookup_definition.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/lookup_table_file.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/outputs.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/outputs_tcp_default.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/outputs_tcp_group.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/outputs_tcp_server.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/outputs_tcp_syslog.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/py.typed +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/sh_indexes_manager.py +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk.egg-info/SOURCES.txt +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk.egg-info/dependency_links.txt +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk.egg-info/requires.txt +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk.egg-info/top_level.txt +0 -0
- {pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/setup.cfg +0 -0
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/config/__init__.pyi
RENAMED
|
@@ -16,8 +16,7 @@ from .. import _utilities
|
|
|
16
16
|
|
|
17
17
|
authToken: Optional[str]
|
|
18
18
|
"""
|
|
19
|
-
Authentication tokens, also known as JSON Web Tokens (JWT), are a method for authenticating Splunk platform users into
|
|
20
|
-
the Splunk platform
|
|
19
|
+
Authentication tokens, also known as JSON Web Tokens (JWT), are a method for authenticating Splunk platform users into the Splunk platform
|
|
21
20
|
"""
|
|
22
21
|
|
|
23
22
|
insecureSkipVerify: Optional[bool]
|
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/config/vars.py
RENAMED
|
@@ -23,8 +23,7 @@ class _ExportableConfig(types.ModuleType):
|
|
|
23
23
|
@_builtins.property
|
|
24
24
|
def auth_token(self) -> Optional[str]:
|
|
25
25
|
"""
|
|
26
|
-
Authentication tokens, also known as JSON Web Tokens (JWT), are a method for authenticating Splunk platform users into
|
|
27
|
-
the Splunk platform
|
|
26
|
+
Authentication tokens, also known as JSON Web Tokens (JWT), are a method for authenticating Splunk platform users into the Splunk platform
|
|
28
27
|
"""
|
|
29
28
|
return __config__.get('authToken')
|
|
30
29
|
|
|
@@ -27,8 +27,7 @@ class ProviderArgs:
|
|
|
27
27
|
username: Optional[pulumi.Input[_builtins.str]] = None):
|
|
28
28
|
"""
|
|
29
29
|
The set of arguments for constructing a Provider resource.
|
|
30
|
-
:param pulumi.Input[_builtins.str] auth_token: Authentication tokens, also known as JSON Web Tokens (JWT), are a method for authenticating Splunk platform users into
|
|
31
|
-
the Splunk platform
|
|
30
|
+
:param pulumi.Input[_builtins.str] auth_token: Authentication tokens, also known as JSON Web Tokens (JWT), are a method for authenticating Splunk platform users into the Splunk platform
|
|
32
31
|
:param pulumi.Input[_builtins.bool] insecure_skip_verify: insecure skip verification flag
|
|
33
32
|
:param pulumi.Input[_builtins.str] password: Splunk instance password
|
|
34
33
|
:param pulumi.Input[_builtins.int] timeout: Timeout when making calls to Splunk server. Defaults to 60 seconds
|
|
@@ -52,8 +51,7 @@ class ProviderArgs:
|
|
|
52
51
|
@pulumi.getter(name="authToken")
|
|
53
52
|
def auth_token(self) -> Optional[pulumi.Input[_builtins.str]]:
|
|
54
53
|
"""
|
|
55
|
-
Authentication tokens, also known as JSON Web Tokens (JWT), are a method for authenticating Splunk platform users into
|
|
56
|
-
the Splunk platform
|
|
54
|
+
Authentication tokens, also known as JSON Web Tokens (JWT), are a method for authenticating Splunk platform users into the Splunk platform
|
|
57
55
|
"""
|
|
58
56
|
return pulumi.get(self, "auth_token")
|
|
59
57
|
|
|
@@ -143,8 +141,7 @@ class Provider(pulumi.ProviderResource):
|
|
|
143
141
|
|
|
144
142
|
:param str resource_name: The name of the resource.
|
|
145
143
|
:param pulumi.ResourceOptions opts: Options for the resource.
|
|
146
|
-
:param pulumi.Input[_builtins.str] auth_token: Authentication tokens, also known as JSON Web Tokens (JWT), are a method for authenticating Splunk platform users into
|
|
147
|
-
the Splunk platform
|
|
144
|
+
:param pulumi.Input[_builtins.str] auth_token: Authentication tokens, also known as JSON Web Tokens (JWT), are a method for authenticating Splunk platform users into the Splunk platform
|
|
148
145
|
:param pulumi.Input[_builtins.bool] insecure_skip_verify: insecure skip verification flag
|
|
149
146
|
:param pulumi.Input[_builtins.str] password: Splunk instance password
|
|
150
147
|
:param pulumi.Input[_builtins.int] timeout: Timeout when making calls to Splunk server. Defaults to 60 seconds
|
|
@@ -209,8 +206,7 @@ class Provider(pulumi.ProviderResource):
|
|
|
209
206
|
@pulumi.getter(name="authToken")
|
|
210
207
|
def auth_token(self) -> pulumi.Output[Optional[_builtins.str]]:
|
|
211
208
|
"""
|
|
212
|
-
Authentication tokens, also known as JSON Web Tokens (JWT), are a method for authenticating Splunk platform users into
|
|
213
|
-
the Splunk platform
|
|
209
|
+
Authentication tokens, also known as JSON Web Tokens (JWT), are a method for authenticating Splunk platform users into the Splunk platform
|
|
214
210
|
"""
|
|
215
211
|
return pulumi.get(self, "auth_token")
|
|
216
212
|
|
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/saved_searches.py
RENAMED
|
@@ -272,21 +272,11 @@ class SavedSearchesArgs:
|
|
|
272
272
|
:param pulumi.Input[_builtins.str] action_slack_param_message: Enter the chat message to send to the Slack channel. The message can include tokens that insert text based on the results of the search.
|
|
273
273
|
:param pulumi.Input[_builtins.str] action_slack_param_webhook_url_override: You can override the Slack webhook URL here if you need to send the alert message to a different Slack team
|
|
274
274
|
:param pulumi.Input[_builtins.str] action_snow_event_param_account: Account(s) for which the event is/ are to be created across ServiceNow instance(s).
|
|
275
|
-
:param pulumi.Input[_builtins.str] action_snow_event_param_additional_info: You can pass additional information that might be of use to the user. This field can also be used to supply the URL of
|
|
276
|
-
|
|
277
|
-
|
|
278
|
-
resulting full URL for navigation from ServiceNow to the Splunk platform search by clicking Splunk Drilldown in the
|
|
279
|
-
event page in ServiceNow. See an example below. Note that if you create events using the commands snowevent or
|
|
280
|
-
snoweventstream, you must supply the URL in this field.You can pass the URL of Splunk as url=<value>. You can also pass
|
|
281
|
-
other fields and their values by || separated key-value format. For example, url=<value>||k1=v1||k2=v2||....
|
|
282
|
-
:param pulumi.Input[_builtins.str] action_snow_event_param_ci_identifier: String that represents a configuration item in your network. You can pass value as || separated key-value format. For
|
|
283
|
-
example, k1=v1||k2=v2.
|
|
284
|
-
:param pulumi.Input[_builtins.str] action_snow_event_param_custom_fields: The custom fields which are configured at the ServiceNow Instance. You can pass the custom fields and their values in
|
|
285
|
-
the || separated format. For example, custom_field1=value1||custom_field2=value2||...custom_fields used must be present
|
|
286
|
-
in the em_event table of ServiceNow.
|
|
275
|
+
:param pulumi.Input[_builtins.str] action_snow_event_param_additional_info: You can pass additional information that might be of use to the user. This field can also be used to supply the URL of your Splunk search head. When you use the snow_event.py alert-triggered script, the Splunk platform uses the URL to create a deep link that allows a ServiceNow user to navigate back to this Splunk platform search. You can find the resulting full URL for navigation from ServiceNow to the Splunk platform search by clicking Splunk Drilldown in the event page in ServiceNow. See an example below. Note that if you create events using the commands snowevent or snoweventstream, you must supply the URL in this field.You can pass the URL of Splunk as url=<value>. You can also pass other fields and their values by || separated key-value format. For example, url=<value>||k1=v1||k2=v2||....
|
|
276
|
+
:param pulumi.Input[_builtins.str] action_snow_event_param_ci_identifier: String that represents a configuration item in your network. You can pass value as || separated key-value format. For example, k1=v1||k2=v2.
|
|
277
|
+
:param pulumi.Input[_builtins.str] action_snow_event_param_custom_fields: The custom fields which are configured at the ServiceNow Instance. You can pass the custom fields and their values in the || separated format. For example, custom_field1=value1||custom_field2=value2||...custom_fields used must be present in the em_event table of ServiceNow.
|
|
287
278
|
:param pulumi.Input[_builtins.str] action_snow_event_param_description: A brief description of the event.
|
|
288
|
-
:param pulumi.Input[_builtins.str] action_snow_event_param_node: The node, formatted to follow your organization's ITIL standards and mapping. If the node value matches a CI with the
|
|
289
|
-
same host name, the event is automatically assigned to the matching CI.
|
|
279
|
+
:param pulumi.Input[_builtins.str] action_snow_event_param_node: The node, formatted to follow your organization's ITIL standards and mapping. If the node value matches a CI with the same host name, the event is automatically assigned to the matching CI.
|
|
290
280
|
:param pulumi.Input[_builtins.str] action_snow_event_param_resource: The resource, formatted to follow your organization's ITIL standards and mapping. For example, resource='CPU'.
|
|
291
281
|
:param pulumi.Input[_builtins.int] action_snow_event_param_severity: The severity associated with the event. 0 - Clear 1 - Critical 2 - Major 3 - Minor 4 - Warning
|
|
292
282
|
:param pulumi.Input[_builtins.str] action_snow_event_param_type: The type, formatted to follow your organization's ITIL standards and mapping. For example, type='Virtual Machine'.
|
|
@@ -1722,13 +1712,7 @@ class SavedSearchesArgs:
|
|
|
1722
1712
|
@pulumi.getter(name="actionSnowEventParamAdditionalInfo")
|
|
1723
1713
|
def action_snow_event_param_additional_info(self) -> Optional[pulumi.Input[_builtins.str]]:
|
|
1724
1714
|
"""
|
|
1725
|
-
You can pass additional information that might be of use to the user. This field can also be used to supply the URL of
|
|
1726
|
-
your Splunk search head. When you use the snow_event.py alert-triggered script, the Splunk platform uses the URL to
|
|
1727
|
-
create a deep link that allows a ServiceNow user to navigate back to this Splunk platform search. You can find the
|
|
1728
|
-
resulting full URL for navigation from ServiceNow to the Splunk platform search by clicking Splunk Drilldown in the
|
|
1729
|
-
event page in ServiceNow. See an example below. Note that if you create events using the commands snowevent or
|
|
1730
|
-
snoweventstream, you must supply the URL in this field.You can pass the URL of Splunk as url=<value>. You can also pass
|
|
1731
|
-
other fields and their values by || separated key-value format. For example, url=<value>||k1=v1||k2=v2||....
|
|
1715
|
+
You can pass additional information that might be of use to the user. This field can also be used to supply the URL of your Splunk search head. When you use the snow_event.py alert-triggered script, the Splunk platform uses the URL to create a deep link that allows a ServiceNow user to navigate back to this Splunk platform search. You can find the resulting full URL for navigation from ServiceNow to the Splunk platform search by clicking Splunk Drilldown in the event page in ServiceNow. See an example below. Note that if you create events using the commands snowevent or snoweventstream, you must supply the URL in this field.You can pass the URL of Splunk as url=<value>. You can also pass other fields and their values by || separated key-value format. For example, url=<value>||k1=v1||k2=v2||....
|
|
1732
1716
|
"""
|
|
1733
1717
|
return pulumi.get(self, "action_snow_event_param_additional_info")
|
|
1734
1718
|
|
|
@@ -1740,8 +1724,7 @@ class SavedSearchesArgs:
|
|
|
1740
1724
|
@pulumi.getter(name="actionSnowEventParamCiIdentifier")
|
|
1741
1725
|
def action_snow_event_param_ci_identifier(self) -> Optional[pulumi.Input[_builtins.str]]:
|
|
1742
1726
|
"""
|
|
1743
|
-
String that represents a configuration item in your network. You can pass value as || separated key-value format. For
|
|
1744
|
-
example, k1=v1||k2=v2.
|
|
1727
|
+
String that represents a configuration item in your network. You can pass value as || separated key-value format. For example, k1=v1||k2=v2.
|
|
1745
1728
|
"""
|
|
1746
1729
|
return pulumi.get(self, "action_snow_event_param_ci_identifier")
|
|
1747
1730
|
|
|
@@ -1753,9 +1736,7 @@ class SavedSearchesArgs:
|
|
|
1753
1736
|
@pulumi.getter(name="actionSnowEventParamCustomFields")
|
|
1754
1737
|
def action_snow_event_param_custom_fields(self) -> Optional[pulumi.Input[_builtins.str]]:
|
|
1755
1738
|
"""
|
|
1756
|
-
The custom fields which are configured at the ServiceNow Instance. You can pass the custom fields and their values in
|
|
1757
|
-
the || separated format. For example, custom_field1=value1||custom_field2=value2||...custom_fields used must be present
|
|
1758
|
-
in the em_event table of ServiceNow.
|
|
1739
|
+
The custom fields which are configured at the ServiceNow Instance. You can pass the custom fields and their values in the || separated format. For example, custom_field1=value1||custom_field2=value2||...custom_fields used must be present in the em_event table of ServiceNow.
|
|
1759
1740
|
"""
|
|
1760
1741
|
return pulumi.get(self, "action_snow_event_param_custom_fields")
|
|
1761
1742
|
|
|
@@ -1779,8 +1760,7 @@ class SavedSearchesArgs:
|
|
|
1779
1760
|
@pulumi.getter(name="actionSnowEventParamNode")
|
|
1780
1761
|
def action_snow_event_param_node(self) -> Optional[pulumi.Input[_builtins.str]]:
|
|
1781
1762
|
"""
|
|
1782
|
-
The node, formatted to follow your organization's ITIL standards and mapping. If the node value matches a CI with the
|
|
1783
|
-
same host name, the event is automatically assigned to the matching CI.
|
|
1763
|
+
The node, formatted to follow your organization's ITIL standards and mapping. If the node value matches a CI with the same host name, the event is automatically assigned to the matching CI.
|
|
1784
1764
|
"""
|
|
1785
1765
|
return pulumi.get(self, "action_snow_event_param_node")
|
|
1786
1766
|
|
|
@@ -2915,21 +2895,11 @@ class _SavedSearchesState:
|
|
|
2915
2895
|
:param pulumi.Input[_builtins.str] action_slack_param_message: Enter the chat message to send to the Slack channel. The message can include tokens that insert text based on the results of the search.
|
|
2916
2896
|
:param pulumi.Input[_builtins.str] action_slack_param_webhook_url_override: You can override the Slack webhook URL here if you need to send the alert message to a different Slack team
|
|
2917
2897
|
:param pulumi.Input[_builtins.str] action_snow_event_param_account: Account(s) for which the event is/ are to be created across ServiceNow instance(s).
|
|
2918
|
-
:param pulumi.Input[_builtins.str] action_snow_event_param_additional_info: You can pass additional information that might be of use to the user. This field can also be used to supply the URL of
|
|
2919
|
-
|
|
2920
|
-
|
|
2921
|
-
resulting full URL for navigation from ServiceNow to the Splunk platform search by clicking Splunk Drilldown in the
|
|
2922
|
-
event page in ServiceNow. See an example below. Note that if you create events using the commands snowevent or
|
|
2923
|
-
snoweventstream, you must supply the URL in this field.You can pass the URL of Splunk as url=<value>. You can also pass
|
|
2924
|
-
other fields and their values by || separated key-value format. For example, url=<value>||k1=v1||k2=v2||....
|
|
2925
|
-
:param pulumi.Input[_builtins.str] action_snow_event_param_ci_identifier: String that represents a configuration item in your network. You can pass value as || separated key-value format. For
|
|
2926
|
-
example, k1=v1||k2=v2.
|
|
2927
|
-
:param pulumi.Input[_builtins.str] action_snow_event_param_custom_fields: The custom fields which are configured at the ServiceNow Instance. You can pass the custom fields and their values in
|
|
2928
|
-
the || separated format. For example, custom_field1=value1||custom_field2=value2||...custom_fields used must be present
|
|
2929
|
-
in the em_event table of ServiceNow.
|
|
2898
|
+
:param pulumi.Input[_builtins.str] action_snow_event_param_additional_info: You can pass additional information that might be of use to the user. This field can also be used to supply the URL of your Splunk search head. When you use the snow_event.py alert-triggered script, the Splunk platform uses the URL to create a deep link that allows a ServiceNow user to navigate back to this Splunk platform search. You can find the resulting full URL for navigation from ServiceNow to the Splunk platform search by clicking Splunk Drilldown in the event page in ServiceNow. See an example below. Note that if you create events using the commands snowevent or snoweventstream, you must supply the URL in this field.You can pass the URL of Splunk as url=<value>. You can also pass other fields and their values by || separated key-value format. For example, url=<value>||k1=v1||k2=v2||....
|
|
2899
|
+
:param pulumi.Input[_builtins.str] action_snow_event_param_ci_identifier: String that represents a configuration item in your network. You can pass value as || separated key-value format. For example, k1=v1||k2=v2.
|
|
2900
|
+
:param pulumi.Input[_builtins.str] action_snow_event_param_custom_fields: The custom fields which are configured at the ServiceNow Instance. You can pass the custom fields and their values in the || separated format. For example, custom_field1=value1||custom_field2=value2||...custom_fields used must be present in the em_event table of ServiceNow.
|
|
2930
2901
|
:param pulumi.Input[_builtins.str] action_snow_event_param_description: A brief description of the event.
|
|
2931
|
-
:param pulumi.Input[_builtins.str] action_snow_event_param_node: The node, formatted to follow your organization's ITIL standards and mapping. If the node value matches a CI with the
|
|
2932
|
-
same host name, the event is automatically assigned to the matching CI.
|
|
2902
|
+
:param pulumi.Input[_builtins.str] action_snow_event_param_node: The node, formatted to follow your organization's ITIL standards and mapping. If the node value matches a CI with the same host name, the event is automatically assigned to the matching CI.
|
|
2933
2903
|
:param pulumi.Input[_builtins.str] action_snow_event_param_resource: The resource, formatted to follow your organization's ITIL standards and mapping. For example, resource='CPU'.
|
|
2934
2904
|
:param pulumi.Input[_builtins.int] action_snow_event_param_severity: The severity associated with the event. 0 - Clear 1 - Critical 2 - Major 3 - Minor 4 - Warning
|
|
2935
2905
|
:param pulumi.Input[_builtins.str] action_snow_event_param_type: The type, formatted to follow your organization's ITIL standards and mapping. For example, type='Virtual Machine'.
|
|
@@ -4414,13 +4384,7 @@ class _SavedSearchesState:
|
|
|
4414
4384
|
@pulumi.getter(name="actionSnowEventParamAdditionalInfo")
|
|
4415
4385
|
def action_snow_event_param_additional_info(self) -> Optional[pulumi.Input[_builtins.str]]:
|
|
4416
4386
|
"""
|
|
4417
|
-
You can pass additional information that might be of use to the user. This field can also be used to supply the URL of
|
|
4418
|
-
your Splunk search head. When you use the snow_event.py alert-triggered script, the Splunk platform uses the URL to
|
|
4419
|
-
create a deep link that allows a ServiceNow user to navigate back to this Splunk platform search. You can find the
|
|
4420
|
-
resulting full URL for navigation from ServiceNow to the Splunk platform search by clicking Splunk Drilldown in the
|
|
4421
|
-
event page in ServiceNow. See an example below. Note that if you create events using the commands snowevent or
|
|
4422
|
-
snoweventstream, you must supply the URL in this field.You can pass the URL of Splunk as url=<value>. You can also pass
|
|
4423
|
-
other fields and their values by || separated key-value format. For example, url=<value>||k1=v1||k2=v2||....
|
|
4387
|
+
You can pass additional information that might be of use to the user. This field can also be used to supply the URL of your Splunk search head. When you use the snow_event.py alert-triggered script, the Splunk platform uses the URL to create a deep link that allows a ServiceNow user to navigate back to this Splunk platform search. You can find the resulting full URL for navigation from ServiceNow to the Splunk platform search by clicking Splunk Drilldown in the event page in ServiceNow. See an example below. Note that if you create events using the commands snowevent or snoweventstream, you must supply the URL in this field.You can pass the URL of Splunk as url=<value>. You can also pass other fields and their values by || separated key-value format. For example, url=<value>||k1=v1||k2=v2||....
|
|
4424
4388
|
"""
|
|
4425
4389
|
return pulumi.get(self, "action_snow_event_param_additional_info")
|
|
4426
4390
|
|
|
@@ -4432,8 +4396,7 @@ class _SavedSearchesState:
|
|
|
4432
4396
|
@pulumi.getter(name="actionSnowEventParamCiIdentifier")
|
|
4433
4397
|
def action_snow_event_param_ci_identifier(self) -> Optional[pulumi.Input[_builtins.str]]:
|
|
4434
4398
|
"""
|
|
4435
|
-
String that represents a configuration item in your network. You can pass value as || separated key-value format. For
|
|
4436
|
-
example, k1=v1||k2=v2.
|
|
4399
|
+
String that represents a configuration item in your network. You can pass value as || separated key-value format. For example, k1=v1||k2=v2.
|
|
4437
4400
|
"""
|
|
4438
4401
|
return pulumi.get(self, "action_snow_event_param_ci_identifier")
|
|
4439
4402
|
|
|
@@ -4445,9 +4408,7 @@ class _SavedSearchesState:
|
|
|
4445
4408
|
@pulumi.getter(name="actionSnowEventParamCustomFields")
|
|
4446
4409
|
def action_snow_event_param_custom_fields(self) -> Optional[pulumi.Input[_builtins.str]]:
|
|
4447
4410
|
"""
|
|
4448
|
-
The custom fields which are configured at the ServiceNow Instance. You can pass the custom fields and their values in
|
|
4449
|
-
the || separated format. For example, custom_field1=value1||custom_field2=value2||...custom_fields used must be present
|
|
4450
|
-
in the em_event table of ServiceNow.
|
|
4411
|
+
The custom fields which are configured at the ServiceNow Instance. You can pass the custom fields and their values in the || separated format. For example, custom_field1=value1||custom_field2=value2||...custom_fields used must be present in the em_event table of ServiceNow.
|
|
4451
4412
|
"""
|
|
4452
4413
|
return pulumi.get(self, "action_snow_event_param_custom_fields")
|
|
4453
4414
|
|
|
@@ -4471,8 +4432,7 @@ class _SavedSearchesState:
|
|
|
4471
4432
|
@pulumi.getter(name="actionSnowEventParamNode")
|
|
4472
4433
|
def action_snow_event_param_node(self) -> Optional[pulumi.Input[_builtins.str]]:
|
|
4473
4434
|
"""
|
|
4474
|
-
The node, formatted to follow your organization's ITIL standards and mapping. If the node value matches a CI with the
|
|
4475
|
-
same host name, the event is automatically assigned to the matching CI.
|
|
4435
|
+
The node, formatted to follow your organization's ITIL standards and mapping. If the node value matches a CI with the same host name, the event is automatically assigned to the matching CI.
|
|
4476
4436
|
"""
|
|
4477
4437
|
return pulumi.get(self, "action_snow_event_param_node")
|
|
4478
4438
|
|
|
@@ -5658,21 +5618,11 @@ class SavedSearches(pulumi.CustomResource):
|
|
|
5658
5618
|
:param pulumi.Input[_builtins.str] action_slack_param_message: Enter the chat message to send to the Slack channel. The message can include tokens that insert text based on the results of the search.
|
|
5659
5619
|
:param pulumi.Input[_builtins.str] action_slack_param_webhook_url_override: You can override the Slack webhook URL here if you need to send the alert message to a different Slack team
|
|
5660
5620
|
:param pulumi.Input[_builtins.str] action_snow_event_param_account: Account(s) for which the event is/ are to be created across ServiceNow instance(s).
|
|
5661
|
-
:param pulumi.Input[_builtins.str] action_snow_event_param_additional_info: You can pass additional information that might be of use to the user. This field can also be used to supply the URL of
|
|
5662
|
-
|
|
5663
|
-
|
|
5664
|
-
resulting full URL for navigation from ServiceNow to the Splunk platform search by clicking Splunk Drilldown in the
|
|
5665
|
-
event page in ServiceNow. See an example below. Note that if you create events using the commands snowevent or
|
|
5666
|
-
snoweventstream, you must supply the URL in this field.You can pass the URL of Splunk as url=<value>. You can also pass
|
|
5667
|
-
other fields and their values by || separated key-value format. For example, url=<value>||k1=v1||k2=v2||....
|
|
5668
|
-
:param pulumi.Input[_builtins.str] action_snow_event_param_ci_identifier: String that represents a configuration item in your network. You can pass value as || separated key-value format. For
|
|
5669
|
-
example, k1=v1||k2=v2.
|
|
5670
|
-
:param pulumi.Input[_builtins.str] action_snow_event_param_custom_fields: The custom fields which are configured at the ServiceNow Instance. You can pass the custom fields and their values in
|
|
5671
|
-
the || separated format. For example, custom_field1=value1||custom_field2=value2||...custom_fields used must be present
|
|
5672
|
-
in the em_event table of ServiceNow.
|
|
5621
|
+
:param pulumi.Input[_builtins.str] action_snow_event_param_additional_info: You can pass additional information that might be of use to the user. This field can also be used to supply the URL of your Splunk search head. When you use the snow_event.py alert-triggered script, the Splunk platform uses the URL to create a deep link that allows a ServiceNow user to navigate back to this Splunk platform search. You can find the resulting full URL for navigation from ServiceNow to the Splunk platform search by clicking Splunk Drilldown in the event page in ServiceNow. See an example below. Note that if you create events using the commands snowevent or snoweventstream, you must supply the URL in this field.You can pass the URL of Splunk as url=<value>. You can also pass other fields and their values by || separated key-value format. For example, url=<value>||k1=v1||k2=v2||....
|
|
5622
|
+
:param pulumi.Input[_builtins.str] action_snow_event_param_ci_identifier: String that represents a configuration item in your network. You can pass value as || separated key-value format. For example, k1=v1||k2=v2.
|
|
5623
|
+
:param pulumi.Input[_builtins.str] action_snow_event_param_custom_fields: The custom fields which are configured at the ServiceNow Instance. You can pass the custom fields and their values in the || separated format. For example, custom_field1=value1||custom_field2=value2||...custom_fields used must be present in the em_event table of ServiceNow.
|
|
5673
5624
|
:param pulumi.Input[_builtins.str] action_snow_event_param_description: A brief description of the event.
|
|
5674
|
-
:param pulumi.Input[_builtins.str] action_snow_event_param_node: The node, formatted to follow your organization's ITIL standards and mapping. If the node value matches a CI with the
|
|
5675
|
-
same host name, the event is automatically assigned to the matching CI.
|
|
5625
|
+
:param pulumi.Input[_builtins.str] action_snow_event_param_node: The node, formatted to follow your organization's ITIL standards and mapping. If the node value matches a CI with the same host name, the event is automatically assigned to the matching CI.
|
|
5676
5626
|
:param pulumi.Input[_builtins.str] action_snow_event_param_resource: The resource, formatted to follow your organization's ITIL standards and mapping. For example, resource='CPU'.
|
|
5677
5627
|
:param pulumi.Input[_builtins.int] action_snow_event_param_severity: The severity associated with the event. 0 - Clear 1 - Critical 2 - Major 3 - Minor 4 - Warning
|
|
5678
5628
|
:param pulumi.Input[_builtins.str] action_snow_event_param_type: The type, formatted to follow your organization's ITIL standards and mapping. For example, type='Virtual Machine'.
|
|
@@ -6416,21 +6366,11 @@ class SavedSearches(pulumi.CustomResource):
|
|
|
6416
6366
|
:param pulumi.Input[_builtins.str] action_slack_param_message: Enter the chat message to send to the Slack channel. The message can include tokens that insert text based on the results of the search.
|
|
6417
6367
|
:param pulumi.Input[_builtins.str] action_slack_param_webhook_url_override: You can override the Slack webhook URL here if you need to send the alert message to a different Slack team
|
|
6418
6368
|
:param pulumi.Input[_builtins.str] action_snow_event_param_account: Account(s) for which the event is/ are to be created across ServiceNow instance(s).
|
|
6419
|
-
:param pulumi.Input[_builtins.str] action_snow_event_param_additional_info: You can pass additional information that might be of use to the user. This field can also be used to supply the URL of
|
|
6420
|
-
|
|
6421
|
-
|
|
6422
|
-
resulting full URL for navigation from ServiceNow to the Splunk platform search by clicking Splunk Drilldown in the
|
|
6423
|
-
event page in ServiceNow. See an example below. Note that if you create events using the commands snowevent or
|
|
6424
|
-
snoweventstream, you must supply the URL in this field.You can pass the URL of Splunk as url=<value>. You can also pass
|
|
6425
|
-
other fields and their values by || separated key-value format. For example, url=<value>||k1=v1||k2=v2||....
|
|
6426
|
-
:param pulumi.Input[_builtins.str] action_snow_event_param_ci_identifier: String that represents a configuration item in your network. You can pass value as || separated key-value format. For
|
|
6427
|
-
example, k1=v1||k2=v2.
|
|
6428
|
-
:param pulumi.Input[_builtins.str] action_snow_event_param_custom_fields: The custom fields which are configured at the ServiceNow Instance. You can pass the custom fields and their values in
|
|
6429
|
-
the || separated format. For example, custom_field1=value1||custom_field2=value2||...custom_fields used must be present
|
|
6430
|
-
in the em_event table of ServiceNow.
|
|
6369
|
+
:param pulumi.Input[_builtins.str] action_snow_event_param_additional_info: You can pass additional information that might be of use to the user. This field can also be used to supply the URL of your Splunk search head. When you use the snow_event.py alert-triggered script, the Splunk platform uses the URL to create a deep link that allows a ServiceNow user to navigate back to this Splunk platform search. You can find the resulting full URL for navigation from ServiceNow to the Splunk platform search by clicking Splunk Drilldown in the event page in ServiceNow. See an example below. Note that if you create events using the commands snowevent or snoweventstream, you must supply the URL in this field.You can pass the URL of Splunk as url=<value>. You can also pass other fields and their values by || separated key-value format. For example, url=<value>||k1=v1||k2=v2||....
|
|
6370
|
+
:param pulumi.Input[_builtins.str] action_snow_event_param_ci_identifier: String that represents a configuration item in your network. You can pass value as || separated key-value format. For example, k1=v1||k2=v2.
|
|
6371
|
+
:param pulumi.Input[_builtins.str] action_snow_event_param_custom_fields: The custom fields which are configured at the ServiceNow Instance. You can pass the custom fields and their values in the || separated format. For example, custom_field1=value1||custom_field2=value2||...custom_fields used must be present in the em_event table of ServiceNow.
|
|
6431
6372
|
:param pulumi.Input[_builtins.str] action_snow_event_param_description: A brief description of the event.
|
|
6432
|
-
:param pulumi.Input[_builtins.str] action_snow_event_param_node: The node, formatted to follow your organization's ITIL standards and mapping. If the node value matches a CI with the
|
|
6433
|
-
same host name, the event is automatically assigned to the matching CI.
|
|
6373
|
+
:param pulumi.Input[_builtins.str] action_snow_event_param_node: The node, formatted to follow your organization's ITIL standards and mapping. If the node value matches a CI with the same host name, the event is automatically assigned to the matching CI.
|
|
6434
6374
|
:param pulumi.Input[_builtins.str] action_snow_event_param_resource: The resource, formatted to follow your organization's ITIL standards and mapping. For example, resource='CPU'.
|
|
6435
6375
|
:param pulumi.Input[_builtins.int] action_snow_event_param_severity: The severity associated with the event. 0 - Clear 1 - Critical 2 - Major 3 - Minor 4 - Warning
|
|
6436
6376
|
:param pulumi.Input[_builtins.str] action_snow_event_param_type: The type, formatted to follow your organization's ITIL standards and mapping. For example, type='Virtual Machine'.
|
|
@@ -7396,13 +7336,7 @@ class SavedSearches(pulumi.CustomResource):
|
|
|
7396
7336
|
@pulumi.getter(name="actionSnowEventParamAdditionalInfo")
|
|
7397
7337
|
def action_snow_event_param_additional_info(self) -> pulumi.Output[_builtins.str]:
|
|
7398
7338
|
"""
|
|
7399
|
-
You can pass additional information that might be of use to the user. This field can also be used to supply the URL of
|
|
7400
|
-
your Splunk search head. When you use the snow_event.py alert-triggered script, the Splunk platform uses the URL to
|
|
7401
|
-
create a deep link that allows a ServiceNow user to navigate back to this Splunk platform search. You can find the
|
|
7402
|
-
resulting full URL for navigation from ServiceNow to the Splunk platform search by clicking Splunk Drilldown in the
|
|
7403
|
-
event page in ServiceNow. See an example below. Note that if you create events using the commands snowevent or
|
|
7404
|
-
snoweventstream, you must supply the URL in this field.You can pass the URL of Splunk as url=<value>. You can also pass
|
|
7405
|
-
other fields and their values by || separated key-value format. For example, url=<value>||k1=v1||k2=v2||....
|
|
7339
|
+
You can pass additional information that might be of use to the user. This field can also be used to supply the URL of your Splunk search head. When you use the snow_event.py alert-triggered script, the Splunk platform uses the URL to create a deep link that allows a ServiceNow user to navigate back to this Splunk platform search. You can find the resulting full URL for navigation from ServiceNow to the Splunk platform search by clicking Splunk Drilldown in the event page in ServiceNow. See an example below. Note that if you create events using the commands snowevent or snoweventstream, you must supply the URL in this field.You can pass the URL of Splunk as url=<value>. You can also pass other fields and their values by || separated key-value format. For example, url=<value>||k1=v1||k2=v2||....
|
|
7406
7340
|
"""
|
|
7407
7341
|
return pulumi.get(self, "action_snow_event_param_additional_info")
|
|
7408
7342
|
|
|
@@ -7410,8 +7344,7 @@ class SavedSearches(pulumi.CustomResource):
|
|
|
7410
7344
|
@pulumi.getter(name="actionSnowEventParamCiIdentifier")
|
|
7411
7345
|
def action_snow_event_param_ci_identifier(self) -> pulumi.Output[_builtins.str]:
|
|
7412
7346
|
"""
|
|
7413
|
-
String that represents a configuration item in your network. You can pass value as || separated key-value format. For
|
|
7414
|
-
example, k1=v1||k2=v2.
|
|
7347
|
+
String that represents a configuration item in your network. You can pass value as || separated key-value format. For example, k1=v1||k2=v2.
|
|
7415
7348
|
"""
|
|
7416
7349
|
return pulumi.get(self, "action_snow_event_param_ci_identifier")
|
|
7417
7350
|
|
|
@@ -7419,9 +7352,7 @@ class SavedSearches(pulumi.CustomResource):
|
|
|
7419
7352
|
@pulumi.getter(name="actionSnowEventParamCustomFields")
|
|
7420
7353
|
def action_snow_event_param_custom_fields(self) -> pulumi.Output[_builtins.str]:
|
|
7421
7354
|
"""
|
|
7422
|
-
The custom fields which are configured at the ServiceNow Instance. You can pass the custom fields and their values in
|
|
7423
|
-
the || separated format. For example, custom_field1=value1||custom_field2=value2||...custom_fields used must be present
|
|
7424
|
-
in the em_event table of ServiceNow.
|
|
7355
|
+
The custom fields which are configured at the ServiceNow Instance. You can pass the custom fields and their values in the || separated format. For example, custom_field1=value1||custom_field2=value2||...custom_fields used must be present in the em_event table of ServiceNow.
|
|
7425
7356
|
"""
|
|
7426
7357
|
return pulumi.get(self, "action_snow_event_param_custom_fields")
|
|
7427
7358
|
|
|
@@ -7437,8 +7368,7 @@ class SavedSearches(pulumi.CustomResource):
|
|
|
7437
7368
|
@pulumi.getter(name="actionSnowEventParamNode")
|
|
7438
7369
|
def action_snow_event_param_node(self) -> pulumi.Output[_builtins.str]:
|
|
7439
7370
|
"""
|
|
7440
|
-
The node, formatted to follow your organization's ITIL standards and mapping. If the node value matches a CI with the
|
|
7441
|
-
same host name, the event is automatically assigned to the matching CI.
|
|
7371
|
+
The node, formatted to follow your organization's ITIL standards and mapping. If the node value matches a CI with the same host name, the event is automatically assigned to the matching CI.
|
|
7442
7372
|
"""
|
|
7443
7373
|
return pulumi.get(self, "action_snow_event_param_node")
|
|
7444
7374
|
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/_utilities.py
RENAMED
|
File without changes
|
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/admin_saml_groups.py
RENAMED
|
File without changes
|
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/apps_local.py
RENAMED
|
File without changes
|
|
File without changes
|
|
File without changes
|
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/config/__init__.py
RENAMED
|
File without changes
|
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/configs_conf.py
RENAMED
|
File without changes
|
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/data_ui_views.py
RENAMED
|
File without changes
|
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/generic_acl.py
RENAMED
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/inputs_monitor.py
RENAMED
|
File without changes
|
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/inputs_script.py
RENAMED
|
File without changes
|
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/inputs_tcp_cooked.py
RENAMED
|
File without changes
|
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/inputs_tcp_raw.py
RENAMED
|
File without changes
|
|
File without changes
|
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/inputs_tcp_ssl.py
RENAMED
|
File without changes
|
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/inputs_udp.py
RENAMED
|
File without changes
|
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/lookup_definition.py
RENAMED
|
File without changes
|
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/lookup_table_file.py
RENAMED
|
File without changes
|
|
File without changes
|
|
File without changes
|
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk/outputs_tcp_group.py
RENAMED
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
{pulumi_splunk-1.3.0a1756363339 → pulumi_splunk-1.3.0a1756506919}/pulumi_splunk.egg-info/SOURCES.txt
RENAMED
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|