JiraConfiguration (u.bd1fbe2ccff02fd1cddfdcb5f1e38e71.awso.0.9.1.doc.awso.kendra.Awso

Sourcetype nonrec t = {

jiraAccountUrl : JiraAccountUrl.t;
(*
The URL of the Jira account. For example, company.atlassian.net.
*)
secretArn : SecretArn.t;
(*
The Amazon Resource Name (ARN) of a secret in Secrets Manager contains the key-value pairs required to connect to your Jira data source. The secret must contain a JSON structure with the following keys: jiraId—The Jira user name or email. jiraCredentials—The Jira API token. For more information, see Using a Jira data source.
*)
useChangeLog : Boolean.t option;
(*
TRUE to use the Jira change log to determine which documents require updating in the index. Depending on the change log's size, it may take longer for Amazon Kendra to use the change log than to scan all of your documents in Jira.
*)
project : Project.t option;
(*
Specify which projects to crawl in your Jira data source. You can specify one or more Jira project IDs.
*)
issueType : IssueType.t option;
(*
Specify which issue types to crawl in your Jira data source. You can specify one or more of these options to crawl.
*)
status : JiraStatus.t option;
(*
Specify which statuses to crawl in your Jira data source. You can specify one or more of these options to crawl.
*)
issueSubEntityFilter : IssueSubEntityFilter.t option;
(*
Specify whether to crawl comments, attachments, and work logs. You can specify one or more of these options.
*)
attachmentFieldMappings : DataSourceToIndexFieldMappingList.t option;
(*
A list of DataSourceToIndexFieldMapping objects that map attributes or field names of Jira attachments to Amazon Kendra index field names. To create custom fields, use the UpdateIndex API before you map to Jira fields. For more information, see Mapping data source fields. The Jira data source field names must exist in your Jira custom metadata.
*)
commentFieldMappings : DataSourceToIndexFieldMappingList.t option;
(*
A list of DataSourceToIndexFieldMapping objects that map attributes or field names of Jira comments to Amazon Kendra index field names. To create custom fields, use the UpdateIndex API before you map to Jira fields. For more information, see Mapping data source fields. The Jira data source field names must exist in your Jira custom metadata.
*)
issueFieldMappings : DataSourceToIndexFieldMappingList.t option;
(*
A list of DataSourceToIndexFieldMapping objects that map attributes or field names of Jira issues to Amazon Kendra index field names. To create custom fields, use the UpdateIndex API before you map to Jira fields. For more information, see Mapping data source fields. The Jira data source field names must exist in your Jira custom metadata.
*)
projectFieldMappings : DataSourceToIndexFieldMappingList.t option;
(*
A list of DataSourceToIndexFieldMapping objects that map attributes or field names of Jira projects to Amazon Kendra index field names. To create custom fields, use the UpdateIndex API before you map to Jira fields. For more information, see Mapping data source fields. The Jira data source field names must exist in your Jira custom metadata.
*)
workLogFieldMappings : DataSourceToIndexFieldMappingList.t option;
(*
A list of DataSourceToIndexFieldMapping objects that map attributes or field names of Jira work logs to Amazon Kendra index field names. To create custom fields, use the UpdateIndex API before you map to Jira fields. For more information, see Mapping data source fields. The Jira data source field names must exist in your Jira custom metadata.
*)
inclusionPatterns : DataSourceInclusionsExclusionsStrings.t option;
(*
A list of regular expression patterns to include certain file paths, file names, and file types in your Jira data source. Files that match the patterns are included in the index. Files that don't match the patterns are excluded from the index. If a file matches both an inclusion pattern and an exclusion pattern, the exclusion pattern takes precedence and the file isn't included in the index.
*)
exclusionPatterns : DataSourceInclusionsExclusionsStrings.t option;
(*
A list of regular expression patterns to exclude certain file paths, file names, and file types in your Jira data source. Files that match the patterns are excluded from the index. Files that don’t match the patterns are included in the index. If a file matches both an inclusion pattern and an exclusion pattern, the exclusion pattern takes precedence and the file isn't included in the index.
*)
vpcConfiguration : DataSourceVpcConfiguration.t option;
(*
Configuration information for an Amazon Virtual Private Cloud to connect to your Jira. For more information, see Configuring a VPC.
*)

}

Sourceval context_ : string

val make : 
  ?useChangeLog:??? ->
  ?project:??? ->
  ?issueType:??? ->
  ?status:??? ->
  ?issueSubEntityFilter:??? ->
  ?attachmentFieldMappings:??? ->
  ?commentFieldMappings:??? ->
  ?issueFieldMappings:??? ->
  ?projectFieldMappings:??? ->
  ?workLogFieldMappings:??? ->
  ?inclusionPatterns:??? ->
  ?exclusionPatterns:??? ->
  ?vpcConfiguration:??? ->
  jiraAccountUrl:JiraAccountUrl.t ->
  secretArn:SecretArn.t ->
  unit ->
  t

Source

val to_value : 
  t ->
  [> `Structure of
       (string
        * [> `Boolean of Boolean.t
          | `List of
            [> `Enum of string
            | `String of String_.t
            | `Structure of
              (string * [> `String of DataSourceFieldName.t ]) list ]
              list
          | `String of JiraAccountUrl.t
          | `Structure of
            (string * [> `List of [> `String of SubnetId.t ] list ]) list ])
         list ]

Sourceval to_query : t -> Awso.Client.Query.t

Sourceval of_xml : Awso.Xml.t -> t

Sourceval of_string : string -> t

Sourceval of_json : Yojson.Safe.t -> t

Sourceval to_json : t -> Yojson.Safe.t