Copyright	(c) 2013-2023 Brendan Hay
License	Mozilla Public License, v. 2.0.
Maintainer	Brendan Hay
Stability	auto-generated
Portability	non-portable (GHC extensions)
Safe Haskell	Safe-Inferred
Language	Haskell2010

Amazonka.DevOpsGuru.Types.ResourceCollection

Description

Documentation

data ResourceCollection Source #

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: newResourceCollection smart constructor.

Constructors

ResourceCollection'

Fields

cloudFormation :: Maybe CloudFormationCollection
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.
tags :: Maybe [TagCollection]
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.

Instances

Instances details

FromJSON ResourceCollection Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.ResourceCollection Methods parseJSON :: Value -> Parser ResourceCollection # parseJSONList :: Value -> Parser [ResourceCollection] #
ToJSON ResourceCollection Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.ResourceCollection Methods toJSON :: ResourceCollection -> Value # toEncoding :: ResourceCollection -> Encoding # toJSONList :: [ResourceCollection] -> Value # toEncodingList :: [ResourceCollection] -> Encoding #
Generic ResourceCollection Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.ResourceCollection Associated Types type Rep ResourceCollection :: Type -> Type # Methods from :: ResourceCollection -> Rep ResourceCollection x # to :: Rep ResourceCollection x -> ResourceCollection #
Read ResourceCollection Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.ResourceCollection Methods readsPrec :: Int -> ReadS ResourceCollection # readList :: ReadS [ResourceCollection] # readPrec :: ReadPrec ResourceCollection # readListPrec :: ReadPrec [ResourceCollection] #
Show ResourceCollection Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.ResourceCollection Methods showsPrec :: Int -> ResourceCollection -> ShowS # show :: ResourceCollection -> String # showList :: [ResourceCollection] -> ShowS #
NFData ResourceCollection Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.ResourceCollection Methods rnf :: ResourceCollection -> () #
Eq ResourceCollection Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.ResourceCollection Methods (==) :: ResourceCollection -> ResourceCollection -> Bool # (/=) :: ResourceCollection -> ResourceCollection -> Bool #
Hashable ResourceCollection Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.ResourceCollection Methods hashWithSalt :: Int -> ResourceCollection -> Int # hash :: ResourceCollection -> Int #
type Rep ResourceCollection Source #
Instance details Defined in Amazonka.DevOpsGuru.Types.ResourceCollection type Rep ResourceCollection = D1 ('MetaData "ResourceCollection" "Amazonka.DevOpsGuru.Types.ResourceCollection" "amazonka-devops-guru-2.0-C03FLSgo73f1Pu5ftIREHS" 'False) (C1 ('MetaCons "ResourceCollection'" 'PrefixI 'True) (S1 ('MetaSel ('Just "cloudFormation") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 (Maybe CloudFormationCollection)) :*: S1 ('MetaSel ('Just "tags") 'NoSourceUnpackedness 'NoSourceStrictness 'DecidedStrict) (Rec0 (Maybe [TagCollection]))))

newResourceCollection :: ResourceCollection Source #

Create a value of ResourceCollection with all optional fields omitted.

Use generic-lens or optics to modify other optional fields.

The following record fields are available, with the corresponding lenses provided for backwards compatibility:

$sel:cloudFormation:ResourceCollection', resourceCollection_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.

$sel:tags:ResourceCollection', resourceCollection_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.

resourceCollection_cloudFormation :: Lens' ResourceCollection (Maybe CloudFormationCollection) Source #

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.

resourceCollection_tags :: Lens' ResourceCollection (Maybe [TagCollection]) Source #

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.