Struct aws_sdk_appsync::operation::put_graphql_api_environment_variables::builders::PutGraphqlApiEnvironmentVariablesInputBuilder

source ·

#[non_exhaustive]
pub struct PutGraphqlApiEnvironmentVariablesInputBuilder { /* private fields */ }

Expand description

A builder for PutGraphqlApiEnvironmentVariablesInput.

Implementations§

source §

impl PutGraphqlApiEnvironmentVariablesInputBuilder

source

pub fn api_id(self, input: impl Into<String>) -> Self

The ID of the API to which the environmental variable list will be written.

This field is required.

source

pub fn set_api_id(self, input: Option<String>) -> Self

The ID of the API to which the environmental variable list will be written.

source

pub fn get_api_id(&self) -> &Option<String>

The ID of the API to which the environmental variable list will be written.

source

pub fn environment_variables( self, k: impl Into<String>, v: impl Into<String> ) -> Self

Adds a key-value pair to environment_variables.

To override the contents of this collection use set_environment_variables.

The list of environmental variables to add to the API.

When creating an environmental variable key-value pair, it must follow the additional constraints below:

Keys must begin with a letter.
Keys must be at least two characters long.
Keys can only contain letters, numbers, and the underscore character (_).
Values can be up to 512 characters long.
You can configure up to 50 key-value pairs in a GraphQL API.

You can create a list of environmental variables by adding it to the environmentVariables payload as a list in the format {"key1":"value1","key2":"value2", …}. Note that each call of the PutGraphqlApiEnvironmentVariables action will result in the overwriting of the existing environmental variable list of that API. This means the existing environmental variables will be lost. To avoid this, you must include all existing and new environmental variables in the list each time you call this action.

source

pub fn set_environment_variables( self, input: Option<HashMap<String, String>> ) -> Self

The list of environmental variables to add to the API.

When creating an environmental variable key-value pair, it must follow the additional constraints below:

Keys must begin with a letter.
Keys must be at least two characters long.
Keys can only contain letters, numbers, and the underscore character (_).
Values can be up to 512 characters long.
You can configure up to 50 key-value pairs in a GraphQL API.

You can create a list of environmental variables by adding it to the environmentVariables payload as a list in the format {"key1":"value1","key2":"value2", …}. Note that each call of the PutGraphqlApiEnvironmentVariables action will result in the overwriting of the existing environmental variable list of that API. This means the existing environmental variables will be lost. To avoid this, you must include all existing and new environmental variables in the list each time you call this action.

source

pub fn get_environment_variables(&self) -> &Option<HashMap<String, String>>

The list of environmental variables to add to the API.

When creating an environmental variable key-value pair, it must follow the additional constraints below:

Keys must begin with a letter.
Keys must be at least two characters long.
Keys can only contain letters, numbers, and the underscore character (_).
Values can be up to 512 characters long.
You can configure up to 50 key-value pairs in a GraphQL API.

You can create a list of environmental variables by adding it to the environmentVariables payload as a list in the format {"key1":"value1","key2":"value2", …}. Note that each call of the PutGraphqlApiEnvironmentVariables action will result in the overwriting of the existing environmental variable list of that API. This means the existing environmental variables will be lost. To avoid this, you must include all existing and new environmental variables in the list each time you call this action.

source