/* * Copyright 2018-2023 Amazon.com, Inc. or its affiliates. All Rights Reserved. * * Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance with * the License. A copy of the License is located at * * http://aws.amazon.com/apache2.0 * * or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR * CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions * and limitations under the License. */ package com.amazonaws.services.devopsguru.model; import java.io.Serializable; import javax.annotation.Generated; import com.amazonaws.protocol.StructuredPojo; import com.amazonaws.protocol.ProtocolMarshaller; /** *
* 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. *
* * @see AWS API * Documentation */ @Generated("com.amazonaws:aws-java-sdk-code-generator") public class ResourceCollection implements Serializable, Cloneable, StructuredPojo { /** ** 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. *
*/ private CloudFormationCollection cloudFormation; /** ** 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
* .
*
* 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. *
* * @param 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 void setCloudFormation(CloudFormationCollection cloudFormation) { this.cloudFormation = 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. *
* * @return 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() { return this.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. *
* * @param 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. * @return Returns a reference to this object so that method calls can be chained together. */ public ResourceCollection withCloudFormation(CloudFormationCollection cloudFormation) { setCloudFormation(cloudFormation); return this; } /** ** 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
.
*
* 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
.
*
* 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 * {@link #setTags(java.util.Collection)} or {@link #withTags(java.util.Collection)} if you want to override the * existing values. *
* * @param 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
.
*
* 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
.
*