Struct aws_sdk_devopsguru::output::DescribeOrganizationResourceCollectionHealthOutput

#[non_exhaustive]
pub struct DescribeOrganizationResourceCollectionHealthOutput {
    pub cloud_formation: Option<Vec<CloudFormationHealth>>,
    pub service: Option<Vec<ServiceHealth>>,
    pub account: Option<Vec<AccountHealth>>,
    pub next_token: Option<String>,
    pub tags: Option<Vec<TagHealth>>,
}

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

cloud_formation: Option<Vec<CloudFormationHealth>>

The returned CloudFormationHealthOverview object that contains an InsightHealthOverview object with the requested system health information.

service: Option<Vec<ServiceHealth>>

An array of ServiceHealth objects that describes the health of the Amazon Web Services services associated with the resources in the collection.

account: Option<Vec<AccountHealth>>

The name of the organization's account.

next_token: Option<String>

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.

tags: Option<Vec<TagHealth>>

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. While keys are case-sensitive, the case of key characters don't matter to DevOps Guru. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers.

Implementations

impl DescribeOrganizationResourceCollectionHealthOutput

pub fn cloud_formation(&self) -> Option<&[CloudFormationHealth]>

The returned CloudFormationHealthOverview object that contains an InsightHealthOverview object with the requested system health information.

pub fn service(&self) -> Option<&[ServiceHealth]>

An array of ServiceHealth objects that describes the health of the Amazon Web Services services associated with the resources in the collection.

pub fn account(&self) -> Option<&[AccountHealth]>

The name of the organization's account.

pub fn next_token(&self) -> Option<&str>

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.

pub fn tags(&self) -> Option<&[TagHealth]>

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. While keys are case-sensitive, the case of key characters don't matter to DevOps Guru. For example, DevOps Guru works with a key named devops-guru-rds and a key named DevOps-Guru-RDS. Possible key/value pairs in your application might be Devops-Guru-production-application/RDS or Devops-Guru-production-application/containers.

impl DescribeOrganizationResourceCollectionHealthOutput

pub fn builder() -> Builder

Creates a new builder-style object to manufacture DescribeOrganizationResourceCollectionHealthOutput.

Trait Implementations

impl Clone for DescribeOrganizationResourceCollectionHealthOutput

fn clone(&self) -> DescribeOrganizationResourceCollectionHealthOutput

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for DescribeOrganizationResourceCollectionHealthOutput

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq<DescribeOrganizationResourceCollectionHealthOutput> for DescribeOrganizationResourceCollectionHealthOutput

fn eq(&self, other: &DescribeOrganizationResourceCollectionHealthOutput) -> bool

This method tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &DescribeOrganizationResourceCollectionHealthOutput) -> bool

This method tests for !=.

impl StructuralPartialEq for DescribeOrganizationResourceCollectionHealthOutput