PostDynamicConfig creates/updates dynamic configuration based on the provided request.

PostDynamicConfig creates/updates dynamic configuration based on the provided request.

Path Parameters

• policy_name string required

application/json

Request Body required

• dynamic_config object

Responses

• 200
• default

---

A successful response.

application/json

• Schema
• Example (from schema)

---

Schema

• object

{}

An unexpected error response.

application/json

• Schema
• Example (from schema)

---

Schema

• code int32

  The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

• details object[]

  A list of messages that carry the error details. There is a common set of message types for APIs to use.

  Array [

  @type string

  A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in path/google.protobuf.Duration). The name should be in a canonical form (e.g., leading "." is not accepted).

  In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme http, https, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows:

  • If no scheme is provided, https is assumed.
  • An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
  • Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)

  Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. As of May 2023, there are no widely used type server implementations and no plans to implement one.

  Schemes other than http, https (or the empty scheme) might be used with implementation specific semantics.

  ]
• message string

  A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.

{
  "code": 0,
  "details": [
    {
      "@type": "string"
    }
  ],
  "message": "string"
}

POST /v1/dynamic-configs/:policy_name

Request

Base URL

https://aperture-controller

policy_name — path required

Body required

{
  "dynamic_config": {}
}

curl / cURL

curl -L -X POST 'https://aperture-controller/v1/dynamic-configs/:policy_name' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
--data-raw '{
  "dynamic_config": {}
}'

python / requests

curl -L -X POST 'https://aperture-controller/v1/dynamic-configs/:policy_name' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
--data-raw '{
  "dynamic_config": {}
}'

go / native

curl -L -X POST 'https://aperture-controller/v1/dynamic-configs/:policy_name' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
--data-raw '{
  "dynamic_config": {}
}'