fn put_organization_config_rule(
        &self,
        input: PutOrganizationConfigRuleRequest,
    ) -> RusotoFuture<PutOrganizationConfigRuleResponse, PutOrganizationConfigRuleError> {
        let mut request = SignedRequest::new("POST", "config", &self.region, "/");

        request.set_content_type("application/x-amz-json-1.1".to_owned());
        request.add_header(
            "x-amz-target",
            "StarlingDoveService.PutOrganizationConfigRule",
        );
        let encoded = serde_json::to_string(&input).unwrap();
        request.set_payload(Some(encoded));

        self.client.sign_and_dispatch(request, |response| {
            if response.status.is_success() {
                Box::new(response.buffer().from_err().and_then(|response| {
                    proto::json::ResponsePayload::new(&response)
                        .deserialize::<PutOrganizationConfigRuleResponse, _>()
                }))
            } else {
                Box::new(response.buffer().from_err().and_then(|response| {
                    Err(PutOrganizationConfigRuleError::from_response(response))
                }))
            }
        })
    }
/// <p><p>Adds or updates organization config rule for your entire organization evaluating whether your AWS resources comply with your desired configurations. Only a master account can create or update an organization config rule.</p> <p>This API enables organization service access through the <code>EnableAWSServiceAccess</code> action and creates a service linked role <code>AWSServiceRoleForConfigMultiAccountSetup</code> in the master account of your organization. The service linked role is created only when the role does not exist in the master account. AWS Config verifies the existence of role with <code>GetRole</code> action.</p> <p>You can use this action to create both custom AWS Config rules and AWS managed Config rules. If you are adding a new custom AWS Config rule, you must first create AWS Lambda function in the master account that the rule invokes to evaluate your resources. When you use the <code>PutOrganizationConfigRule</code> action to add the rule to AWS Config, you must specify the Amazon Resource Name (ARN) that AWS Lambda assigns to the function. If you are adding an AWS managed Config rule, specify the rule&#39;s identifier for the <code>RuleIdentifier</code> key.</p> <p>The maximum number of organization config rules that AWS Config supports is 150.</p> <note> <p>Specify either <code>OrganizationCustomRuleMetadata</code> or <code>OrganizationManagedRuleMetadata</code>.</p> </note></p>
Adds or updates organization config rule for your entire organization evaluating whether your AWS resources comply with your desired configurations. Only a master account can create or update an organization config rule. This API enables organization service access through the EnableAWSServiceAccess action and creates a service linked role AWSServiceRoleForConfigMultiAccountSetup in the master account of your organization. The service linked role is created only when the role does not exist in the master account. AWS Config verifies the existence of role with GetRole action. You can use this action to create both custom AWS Config rules and AWS managed Config rules. If you are adding a new custom AWS Config rule, you must first create AWS Lambda function in the master account that the rule invokes to evaluate your resources. When you use the PutOrganizationConfigRule action to add the rule to AWS Config, you must specify the Amazon Resource Name (ARN) that AWS Lambda assigns to the function. If you are adding an AWS managed Config rule, specify the rule's identifier for the RuleIdentifier key. The maximum number of organization config rules that AWS Config supports is 150.  Specify either OrganizationCustomRuleMetadata or OrganizationManagedRuleMetadata. 
Adds or updates organization config rule for your entire organization evaluating whether your AWS resources comply with your desired configurations . Only a master account can create or update an organization config rule . This API enables organization service access through the EnableAWSServiceAccess action and creates a service linked role AWSServiceRoleForConfigMultiAccountSetup in the master account of your organization . The service linked role is created only when the role does not exist in the master account . AWS Config verifies the existence of role with GetRole action . You can use this action to create both custom AWS Config rules and AWS managed Config rules . If you are adding a new custom AWS Config rule you must first create AWS Lambda function in the master account that the rule invokes to evaluate your resources . When you use the PutOrganizationConfigRule action to add the rule to AWS Config you must specify the Amazon Resource Name ( ARN ) that AWS Lambda assigns to the function . If you are adding an AWS managed Config rule specify the rule ' s identifier for the RuleIdentifier key . The maximum number of organization config rules that AWS Config supports is 150 . Specify either OrganizationCustomRuleMetadata or OrganizationManagedRuleMetadata .
fn put_organization_config_rule(
        &self,
        input: PutOrganizationConfigRuleRequest,
    ) -> RusotoFuture<PutOrganizationConfigRuleResponse, PutOrganizationConfigRuleError> {
        let mut request = SignedRequest::new("POST", "config", &self.region, "/");
        request.set_content_type("application/x-amz-json-1.1".to_owned());
        request.add_header(
            "x-amz-target",
            "StarlingDoveService.PutOrganizationConfigRule",
        );
        let encoded = serde_json::to_string(&input).unwrap();
        request.set_payload(Some(encoded));
        self.client.sign_and_dispatch(request, |response| {
            if response.status.is_success() {
                Box::new(response.buffer().from_err().and_then(|response| {
                    proto::json::ResponsePayload::new(&response)
                        .deserialize::<PutOrganizationConfigRuleResponse, _>()
                }))
            } else {
                Box::new(response.buffer().from_err().and_then(|response| {
                    Err(PutOrganizationConfigRuleError::from_response(response))
                }))
            }
        })
    }
fn put_organization_config_rule ( & self , input : PutOrganizationConfigRuleRequest , ) -> RusotoFuture < PutOrganizationConfigRuleResponse , PutOrganizationConfigRuleError > { let mut request = SignedRequest :: new ( " " , " " , & self . region , " " ) ; request . set_content_type ( " " . to_owned ( ) ) ; request . add_header ( " " , " " , ) ; let encoded = serde_json :: to_string ( & input ) . unwrap ( ) ; request . set_payload ( Some ( encoded ) ) ; self . client . sign_and_dispatch ( request , | response | { if response . status . is_success ( ) { Box :: new ( response . buffer ( ) . from_err ( ) . and_then ( | response | { proto :: json :: ResponsePayload :: new ( & response ) . deserialize :: < PutOrganizationConfigRuleResponse , _ > ( ) } ) ) } else { Box :: new ( response . buffer ( ) . from_err ( ) . and_then ( | response | { Err ( PutOrganizationConfigRuleError :: from_response ( response ) ) } ) ) } } ) }
<p><p>Adds or updates organization config rule for your entire organization evaluating whether your AWS resources comply with your desired configurations.
<p > <p > Adds or updates organization config rule for your entire organization evaluating whether your AWS resources comply with your desired configurations .
&self
input
PutOrganizationConfigRuleRequest