Skip to content

Commit 88ac745

Browse files
author
AWS
committed
AWSKendraFrontendService Update: Amazon Kendra now provides a data source connector for Jira. For more information, see https://docs.aws.amazon.com/kendra/latest/dg/data-source-jira.html
1 parent c7cc6a4 commit 88ac745

File tree

2 files changed

+113
-1
lines changed

2 files changed

+113
-1
lines changed
Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
{
2+
"type": "feature",
3+
"category": "AWSKendraFrontendService",
4+
"contributor": "",
5+
"description": "Amazon Kendra now provides a data source connector for Jira. For more information, see https://docs.aws.amazon.com/kendra/latest/dg/data-source-jira.html"
6+
}

services/kendra/src/main/resources/codegen-resources/service-2.json

Lines changed: 107 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2338,6 +2338,10 @@
23382338
"QuipConfiguration":{
23392339
"shape":"QuipConfiguration",
23402340
"documentation":"<p>Provides the configuration information to connect to Quip as your data source.</p>"
2341+
},
2342+
"JiraConfiguration":{
2343+
"shape":"JiraConfiguration",
2344+
"documentation":"<p>Provides the configuration information to connect to Jira as your data source.</p>"
23412345
}
23422346
},
23432347
"documentation":"<p>Provides the configuration information for an Amazon Kendra data source.</p>"
@@ -2601,7 +2605,8 @@
26012605
"FSX",
26022606
"SLACK",
26032607
"BOX",
2604-
"QUIP"
2608+
"QUIP",
2609+
"JIRA"
26052610
]
26062611
},
26072612
"DataSourceVpcConfiguration":{
@@ -4621,12 +4626,109 @@
46214626
"documentation":"<p>The input to the request is not valid.</p>",
46224627
"exception":true
46234628
},
4629+
"IssueSubEntity":{
4630+
"type":"string",
4631+
"enum":[
4632+
"COMMENTS",
4633+
"ATTACHMENTS",
4634+
"WORKLOGS"
4635+
]
4636+
},
4637+
"IssueSubEntityFilter":{
4638+
"type":"list",
4639+
"member":{"shape":"IssueSubEntity"},
4640+
"max":3,
4641+
"min":0
4642+
},
4643+
"IssueType":{
4644+
"type":"list",
4645+
"member":{"shape":"String"}
4646+
},
46244647
"Issuer":{
46254648
"type":"string",
46264649
"max":65,
46274650
"min":1,
46284651
"pattern":"^\\P{C}*$"
46294652
},
4653+
"JiraAccountUrl":{
4654+
"type":"string",
4655+
"max":2048,
4656+
"min":1,
4657+
"pattern":"^https:\\/\\/[a-zA-Z0-9_\\-\\.]+(\\.atlassian\\.net\\/)$"
4658+
},
4659+
"JiraConfiguration":{
4660+
"type":"structure",
4661+
"required":[
4662+
"JiraAccountUrl",
4663+
"SecretArn"
4664+
],
4665+
"members":{
4666+
"JiraAccountUrl":{
4667+
"shape":"JiraAccountUrl",
4668+
"documentation":"<p>The URL of the Jira account. For example, company.attlassian.net or https://jira.company.com. You can find your Jira account URL in the URL of your profile page for Jira desktop.</p>"
4669+
},
4670+
"SecretArn":{
4671+
"shape":"SecretArn",
4672+
"documentation":"<p>The Amazon Resource Name (ARN) of an Secrets Manager secret that contains the key-value pairs required to connect to your Jira data source. The secret must contain a JSON structure with the following keys:</p> <ul> <li> <p>jira-id—The Active Directory user name, along with the Domain Name System (DNS) domain name. For example, <i>[email protected]</i>.</p> </li> <li> <p>jiraCredentials—The password of the Jira account user.</p> </li> </ul>"
4673+
},
4674+
"UseChangeLog":{
4675+
"shape":"Boolean",
4676+
"documentation":"<p>Specify to use the change log option to update your index.</p>"
4677+
},
4678+
"Project":{
4679+
"shape":"Project",
4680+
"documentation":"<p>Specify which projects to crawl in your Jira data source. You can specify one or more Jira project IDs.</p>"
4681+
},
4682+
"IssueType":{
4683+
"shape":"IssueType",
4684+
"documentation":"<p>Specify which issue types to crawl in your Jira data source. You can specify one or more of these options to crawl.</p>"
4685+
},
4686+
"Status":{
4687+
"shape":"JiraStatus",
4688+
"documentation":"<p>Specify which statuses to crawl in your Jira data source. You can specify one or more of these options to crawl.</p>"
4689+
},
4690+
"IssueSubEntityFilter":{
4691+
"shape":"IssueSubEntityFilter",
4692+
"documentation":"<p>Specify whether to crawl comments, attachments, and work logs. You can specify one or more of these options.</p>"
4693+
},
4694+
"AttachmentFieldMappings":{
4695+
"shape":"DataSourceToIndexFieldMappingList",
4696+
"documentation":"<p>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 <a href=\"https://docs.aws.amazon.com/kendra/latest/dg/field-mapping.html\"> Mapping data source fields</a>. The Jira data source field names must exist in your Jira custom metadata.</p>"
4697+
},
4698+
"CommentFieldMappings":{
4699+
"shape":"DataSourceToIndexFieldMappingList",
4700+
"documentation":"<p>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 <a href=\"https://docs.aws.amazon.com/kendra/latest/dg/field-mapping.html\"> Mapping data source fields</a>. The Jira data source field names must exist in your Jira custom metadata.</p>"
4701+
},
4702+
"IssueFieldMappings":{
4703+
"shape":"DataSourceToIndexFieldMappingList",
4704+
"documentation":"<p>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 <a href=\"https://docs.aws.amazon.com/kendra/latest/dg/field-mapping.html\"> Mapping data source fields</a>. The Jira data source field names must exist in your Jira custom metadata.</p>"
4705+
},
4706+
"ProjectFieldMappings":{
4707+
"shape":"DataSourceToIndexFieldMappingList",
4708+
"documentation":"<p>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 <a href=\"https://docs.aws.amazon.com/kendra/latest/dg/field-mapping.html\"> Mapping data source fields</a>. The Jira data source field names must exist in your Jira custom metadata.</p>"
4709+
},
4710+
"WorkLogFieldMappings":{
4711+
"shape":"DataSourceToIndexFieldMappingList",
4712+
"documentation":"<p>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 <a href=\"https://docs.aws.amazon.com/kendra/latest/dg/field-mapping.html\"> Mapping data source fields</a>. The Jira data source field names must exist in your Jira custom metadata.</p>"
4713+
},
4714+
"InclusionPatterns":{
4715+
"shape":"DataSourceInclusionsExclusionsStrings",
4716+
"documentation":"<p>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.</p>"
4717+
},
4718+
"ExclusionPatterns":{
4719+
"shape":"DataSourceInclusionsExclusionsStrings",
4720+
"documentation":"<p>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.</p>"
4721+
},
4722+
"VpcConfiguration":{
4723+
"shape":"DataSourceVpcConfiguration",
4724+
"documentation":"<p>Configuration information for an Amazon Virtual Private Cloud to connect to your Jira. Your Jira account must reside inside your VPC.</p>"
4725+
}
4726+
}
4727+
},
4728+
"JiraStatus":{
4729+
"type":"list",
4730+
"member":{"shape":"String"}
4731+
},
46304732
"JsonTokenTypeConfiguration":{
46314733
"type":"structure",
46324734
"required":[
@@ -5404,6 +5506,10 @@
54045506
"type":"list",
54055507
"member":{"shape":"String"}
54065508
},
5509+
"Project":{
5510+
"type":"list",
5511+
"member":{"shape":"String"}
5512+
},
54075513
"ProxyConfiguration":{
54085514
"type":"structure",
54095515
"required":[

0 commit comments

Comments
 (0)