Skip to content

Commit 849cbf9

Browse files
author
AWS
committed
Amazon DevOps Guru Update: Adds Tags support to DescribeOrganizationResourceCollectionHealth
1 parent 80a1d42 commit 849cbf9

File tree

3 files changed

+14
-2
lines changed

3 files changed

+14
-2
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": "Amazon DevOps Guru",
4+
"contributor": "",
5+
"description": "Adds Tags support to DescribeOrganizationResourceCollectionHealth"
6+
}

services/devopsguru/src/main/resources/codegen-resources/paginators-1.json

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,8 @@
66
"result_key": [
77
"CloudFormation",
88
"Account",
9-
"Service"
9+
"Service",
10+
"Tags"
1011
]
1112
},
1213
"DescribeResourceCollectionHealth": {

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

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1156,6 +1156,10 @@
11561156
"NextToken":{
11571157
"shape":"UuidNextToken",
11581158
"documentation":"<p>The pagination token to use to retrieve the next page of results for this operation. If there are no more pages, this value is null.</p>"
1159+
},
1160+
"Tags":{
1161+
"shape":"TagHealths",
1162+
"documentation":"<p>Tags help you identify and organize your Amazon Web Services resources. Many Amazon Web Services services support tagging, so you can assign the same tag to resources from different services to indicate that the resources are related. For example, you can assign the same tag to an Amazon DynamoDB table resource that you assign to an Lambda function. For more information about using tags, see the <a href=\"https://d1.awsstatic.com/whitepapers/aws-tagging-best-practices.pdf\">Tagging best practices</a> whitepaper. </p> <p>Each Amazon Web Services tag has two parts. </p> <ul> <li> <p>A tag <i>key</i> (for example, <code>CostCenter</code>, <code>Environment</code>, <code>Project</code>, or <code>Secret</code>). Tag <i>keys</i> are case-sensitive.</p> </li> <li> <p>An optional field known as a tag <i>value</i> (for example, <code>111122223333</code>, <code>Production</code>, or a team name). Omitting the tag <i>value</i> is the same as using an empty string. Like tag <i>keys</i>, tag <i>values</i> are case-sensitive.</p> </li> </ul> <p>Together these are known as <i>key</i>-<i>value</i> pairs.</p> <important> <p>The string used for a <i>key</i> in a tag that you use to define your resource coverage must begin with the prefix <code>Devops-guru-</code>. The tag <i>key</i> might be <code>Devops-guru-deployment-application</code> or <code>Devops-guru-rds-application</code>. While <i>keys</i> are case-sensitive, the case of <i>key</i> characters don't matter to DevOps Guru. For example, DevOps Guru works with a <i>key</i> named <code>devops-guru-rds</code> and a <i>key</i> named <code>DevOps-Guru-RDS</code>. Possible <i>key</i>/<i>value</i> pairs in your application might be <code>Devops-Guru-production-application/RDS</code> or <code>Devops-Guru-production-application/containers</code>.</p> </important>"
11591163
}
11601164
}
11611165
},
@@ -1968,7 +1972,8 @@
19681972
"enum":[
19691973
"AWS_CLOUD_FORMATION",
19701974
"AWS_SERVICE",
1971-
"AWS_ACCOUNT"
1975+
"AWS_ACCOUNT",
1976+
"AWS_TAGS"
19721977
]
19731978
},
19741979
"OrganizationalUnitId":{

0 commit comments

Comments
 (0)