@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class ResourceCollection extends Object implements Serializable, Cloneable, StructuredPojo
A collection of Amazon Web Services resources supported by DevOps Guru. The two types of Amazon Web Services resource collections supported are Amazon Web Services CloudFormation stacks and Amazon Web Services resources that contain the same Amazon Web Services tag. DevOps Guru can be configured to analyze the Amazon Web Services resources that are defined in the stacks or that are tagged using the same tag key. You can specify up to 500 Amazon Web Services CloudFormation stacks.
| Constructor and Description | 
|---|
| ResourceCollection() | 
| Modifier and Type | Method and Description | 
|---|---|
| ResourceCollection | clone() | 
| boolean | equals(Object obj) | 
| CloudFormationCollection | getCloudFormation()
 An array of the names of Amazon Web Services CloudFormation stacks. | 
| List<TagCollection> | getTags()
 The Amazon Web Services tags that are used by resources in the resource collection. | 
| int | hashCode() | 
| void | marshall(ProtocolMarshaller protocolMarshaller)Marshalls this structured data using the given  ProtocolMarshaller. | 
| void | setCloudFormation(CloudFormationCollection cloudFormation)
 An array of the names of Amazon Web Services CloudFormation stacks. | 
| void | setTags(Collection<TagCollection> tags)
 The Amazon Web Services tags that are used by resources in the resource collection. | 
| String | toString()Returns a string representation of this object. | 
| ResourceCollection | withCloudFormation(CloudFormationCollection cloudFormation)
 An array of the names of Amazon Web Services CloudFormation stacks. | 
| ResourceCollection | withTags(Collection<TagCollection> tags)
 The Amazon Web Services tags that are used by resources in the resource collection. | 
| ResourceCollection | withTags(TagCollection... tags)
 The Amazon Web Services tags that are used by resources in the resource collection. | 
public void setCloudFormation(CloudFormationCollection cloudFormation)
An array of the names of Amazon Web Services CloudFormation stacks. The stacks define Amazon Web Services resources that DevOps Guru analyzes. You can specify up to 500 Amazon Web Services CloudFormation stacks.
cloudFormation - An array of the names of Amazon Web Services CloudFormation stacks. The stacks define Amazon Web Services
        resources that DevOps Guru analyzes. You can specify up to 500 Amazon Web Services CloudFormation stacks.public CloudFormationCollection getCloudFormation()
An array of the names of Amazon Web Services CloudFormation stacks. The stacks define Amazon Web Services resources that DevOps Guru analyzes. You can specify up to 500 Amazon Web Services CloudFormation stacks.
public ResourceCollection withCloudFormation(CloudFormationCollection cloudFormation)
An array of the names of Amazon Web Services CloudFormation stacks. The stacks define Amazon Web Services resources that DevOps Guru analyzes. You can specify up to 500 Amazon Web Services CloudFormation stacks.
cloudFormation - An array of the names of Amazon Web Services CloudFormation stacks. The stacks define Amazon Web Services
        resources that DevOps Guru analyzes. You can specify up to 500 Amazon Web Services CloudFormation stacks.public List<TagCollection> getTags()
The Amazon Web Services tags that are used by resources in the resource collection.
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 Tagging best practices whitepaper.
Each Amazon Web Services tag has two parts.
 A tag key (for example, CostCenter, Environment, Project, or
 Secret). Tag keys are case-sensitive.
 
 An optional field known as a tag value (for example, 111122223333, Production,
 or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag
 values are case-sensitive.
 
Together these are known as key-value pairs.
 The string used for a key in a tag that you use to define your resource coverage must begin with the
 prefix Devops-guru-. The tag key might be DevOps-Guru-deployment-application or
 devops-guru-rds-application. When you create a key, the case of characters in the key
 can be whatever you choose. After you create a key, it is case-sensitive. For example, DevOps Guru works
 with a key named devops-guru-rds and a key named DevOps-Guru-RDS, and
 these act as two different keys. Possible key/value pairs in your application might be
 Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers
 .
 
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 Tagging best practices whitepaper.
Each Amazon Web Services tag has two parts.
         A tag key (for example, CostCenter, Environment, Project,
         or Secret). Tag keys are case-sensitive.
         
         An optional field known as a tag value (for example, 111122223333,
         Production, or a team name). Omitting the tag value is the same as using an empty
         string. Like tag keys, tag values are case-sensitive.
         
Together these are known as key-value pairs.
         The string used for a key in a tag that you use to define your resource coverage must begin with
         the prefix Devops-guru-. The tag key might be
         DevOps-Guru-deployment-application or devops-guru-rds-application. When you
         create a key, the case of characters in the key can be whatever you choose. After you
         create a key, it is case-sensitive. For example, DevOps Guru works with a key named
         devops-guru-rds and a key named DevOps-Guru-RDS, and these act as two
         different keys. Possible key/value pairs in your application might be
         Devops-Guru-production-application/RDS or
         Devops-Guru-production-application/containers.
         
public void setTags(Collection<TagCollection> tags)
The Amazon Web Services tags that are used by resources in the resource collection.
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 Tagging best practices whitepaper.
Each Amazon Web Services tag has two parts.
 A tag key (for example, CostCenter, Environment, Project, or
 Secret). Tag keys are case-sensitive.
 
 An optional field known as a tag value (for example, 111122223333, Production,
 or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag
 values are case-sensitive.
 
Together these are known as key-value pairs.
 The string used for a key in a tag that you use to define your resource coverage must begin with the
 prefix Devops-guru-. The tag key might be DevOps-Guru-deployment-application or
 devops-guru-rds-application. When you create a key, the case of characters in the key
 can be whatever you choose. After you create a key, it is case-sensitive. For example, DevOps Guru works
 with a key named devops-guru-rds and a key named DevOps-Guru-RDS, and
 these act as two different keys. Possible key/value pairs in your application might be
 Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers
 .
 
tags - The Amazon Web Services tags that are used by resources in the resource collection.
        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 Tagging best practices whitepaper.
Each Amazon Web Services tag has two parts.
        A tag key (for example, CostCenter, Environment, Project, or
        Secret). Tag keys are case-sensitive.
        
        An optional field known as a tag value (for example, 111122223333,
        Production, or a team name). Omitting the tag value is the same as using an empty
        string. Like tag keys, tag values are case-sensitive.
        
Together these are known as key-value pairs.
        The string used for a key in a tag that you use to define your resource coverage must begin with
        the prefix Devops-guru-. The tag key might be
        DevOps-Guru-deployment-application or devops-guru-rds-application. When you
        create a key, the case of characters in the key can be whatever you choose. After you create
        a key, it is case-sensitive. For example, DevOps Guru works with a key named
        devops-guru-rds and a key named DevOps-Guru-RDS, and these act as two
        different keys. Possible key/value pairs in your application might be
        Devops-Guru-production-application/RDS or
        Devops-Guru-production-application/containers.
        
public ResourceCollection withTags(TagCollection... tags)
The Amazon Web Services tags that are used by resources in the resource collection.
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 Tagging best practices whitepaper.
Each Amazon Web Services tag has two parts.
 A tag key (for example, CostCenter, Environment, Project, or
 Secret). Tag keys are case-sensitive.
 
 An optional field known as a tag value (for example, 111122223333, Production,
 or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag
 values are case-sensitive.
 
Together these are known as key-value pairs.
 The string used for a key in a tag that you use to define your resource coverage must begin with the
 prefix Devops-guru-. The tag key might be DevOps-Guru-deployment-application or
 devops-guru-rds-application. When you create a key, the case of characters in the key
 can be whatever you choose. After you create a key, it is case-sensitive. For example, DevOps Guru works
 with a key named devops-guru-rds and a key named DevOps-Guru-RDS, and
 these act as two different keys. Possible key/value pairs in your application might be
 Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers
 .
 
 NOTE: This method appends the values to the existing list (if any). Use
 setTags(java.util.Collection) or withTags(java.util.Collection) if you want to override the
 existing values.
 
tags - The Amazon Web Services tags that are used by resources in the resource collection.
        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 Tagging best practices whitepaper.
Each Amazon Web Services tag has two parts.
        A tag key (for example, CostCenter, Environment, Project, or
        Secret). Tag keys are case-sensitive.
        
        An optional field known as a tag value (for example, 111122223333,
        Production, or a team name). Omitting the tag value is the same as using an empty
        string. Like tag keys, tag values are case-sensitive.
        
Together these are known as key-value pairs.
        The string used for a key in a tag that you use to define your resource coverage must begin with
        the prefix Devops-guru-. The tag key might be
        DevOps-Guru-deployment-application or devops-guru-rds-application. When you
        create a key, the case of characters in the key can be whatever you choose. After you create
        a key, it is case-sensitive. For example, DevOps Guru works with a key named
        devops-guru-rds and a key named DevOps-Guru-RDS, and these act as two
        different keys. Possible key/value pairs in your application might be
        Devops-Guru-production-application/RDS or
        Devops-Guru-production-application/containers.
        
public ResourceCollection withTags(Collection<TagCollection> tags)
The Amazon Web Services tags that are used by resources in the resource collection.
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 Tagging best practices whitepaper.
Each Amazon Web Services tag has two parts.
 A tag key (for example, CostCenter, Environment, Project, or
 Secret). Tag keys are case-sensitive.
 
 An optional field known as a tag value (for example, 111122223333, Production,
 or a team name). Omitting the tag value is the same as using an empty string. Like tag keys, tag
 values are case-sensitive.
 
Together these are known as key-value pairs.
 The string used for a key in a tag that you use to define your resource coverage must begin with the
 prefix Devops-guru-. The tag key might be DevOps-Guru-deployment-application or
 devops-guru-rds-application. When you create a key, the case of characters in the key
 can be whatever you choose. After you create a key, it is case-sensitive. For example, DevOps Guru works
 with a key named devops-guru-rds and a key named DevOps-Guru-RDS, and
 these act as two different keys. Possible key/value pairs in your application might be
 Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers
 .
 
tags - The Amazon Web Services tags that are used by resources in the resource collection.
        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 Tagging best practices whitepaper.
Each Amazon Web Services tag has two parts.
        A tag key (for example, CostCenter, Environment, Project, or
        Secret). Tag keys are case-sensitive.
        
        An optional field known as a tag value (for example, 111122223333,
        Production, or a team name). Omitting the tag value is the same as using an empty
        string. Like tag keys, tag values are case-sensitive.
        
Together these are known as key-value pairs.
        The string used for a key in a tag that you use to define your resource coverage must begin with
        the prefix Devops-guru-. The tag key might be
        DevOps-Guru-deployment-application or devops-guru-rds-application. When you
        create a key, the case of characters in the key can be whatever you choose. After you create
        a key, it is case-sensitive. For example, DevOps Guru works with a key named
        devops-guru-rds and a key named DevOps-Guru-RDS, and these act as two
        different keys. Possible key/value pairs in your application might be
        Devops-Guru-production-application/RDS or
        Devops-Guru-production-application/containers.
        
public String toString()
toString in class ObjectObject.toString()public ResourceCollection clone()
public void marshall(ProtocolMarshaller protocolMarshaller)
StructuredPojoProtocolMarshaller.marshall in interface StructuredPojoprotocolMarshaller - Implementation of ProtocolMarshaller used to marshall this object's data.