A feature of the API Gateway control service for updating an existing API with an input of external API definitions
Source:R/apigateway_operations.R
apigateway_put_rest_api.RdA feature of the API Gateway control service for updating an existing API with an input of external API definitions. The update can take the form of merging the supplied definition into the existing API or overwriting the existing API.
See https://www.paws-r-sdk.com/docs/apigateway_put_rest_api/ for full documentation.
Usage
apigateway_put_rest_api(
restApiId,
mode = NULL,
failOnWarnings = NULL,
parameters = NULL,
body
)Arguments
- restApiId
[required] The string identifier of the associated RestApi.
- mode
The
modequery parameter to specify the update mode. Valid values are "merge" and "overwrite". By default, the update mode is "merge".- failOnWarnings
A query parameter to indicate whether to rollback the API update (
true) or not (false) when a warning is encountered. The default value isfalse.- parameters
Custom header parameters as part of the request. For example, to exclude DocumentationParts from an imported API, set
ignore=documentationas aparametersvalue, as in the AWS CLI command ofaws apigateway import-rest-api --parameters ignore=documentation --body 'file:///path/to/imported-api-body.json'.- body
[required] The PUT request body containing external API definitions. Currently, only OpenAPI definition JSON/YAML files are supported. The maximum size of the API definition file is 6MB.