Api Config Args
An API Configuration is an association of an API Controller Config and a Gateway Config To get more information about ApiConfig, see:
How-to Guides
Example Usage
Import
ApiConfig can be imported using any of these accepted formats:
projects/{{project}}/locations/global/apis/{{api}}/configs/{{api_config_id}}
{{project}}/{{api}}/{{api_config_id}}
{{api}}/{{api_config_id}}
When using thepulumi import
command, ApiConfig can be imported using one of the formats above. For example:
$ pulumi import gcp:apigateway/apiConfig:ApiConfig default projects/{{project}}/locations/global/apis/{{api}}/configs/{{api_config_id}}
$ pulumi import gcp:apigateway/apiConfig:ApiConfig default {{project}}/{{api}}/{{api_config_id}}
$ pulumi import gcp:apigateway/apiConfig:ApiConfig default {{api}}/{{api_config_id}}
Constructors
Properties
Identifier to assign to the API Config. Must be unique within scope of the parent resource(api).
Creates a unique name beginning with the specified prefix. If this and api_config_id are unspecified, a random value is chosen for the name.
A user-visible name for the API.
Immutable. Gateway specific configuration. If not specified, backend authentication will be set to use OIDC authentication using the default compute service account Structure is documented below.
gRPC service definition files. If specified, openapiDocuments must not be included. Structure is documented below.
Optional. Service Configuration files. At least one must be included when using gRPC service definitions. See https://cloud.google.com/endpoints/docs/grpc/grpc-service-config#service_configuration_overview for the expected file contents. If multiple files are specified, the files are merged with the following rules: * All singular scalar fields are merged using "last one wins" semantics in the order of the files uploaded. * Repeated fields are concatenated. * Singular embedded messages are merged using these rules for nested fields. Structure is documented below.
OpenAPI specification documents. If specified, grpcServices and managedServiceConfigs must not be included. Structure is documented below.