pub struct CreateNamespaceResponse {
pub context: Option<HashMap<String, String>>,
pub transaction_id: Option<String>,
pub properties: Option<HashMap<String, String>>,
}Fields§
§context: Option<HashMap<String, String>>Arbitrary context as key-value pairs. How to use the context is custom to the specific implementation. On a request, it carries caller-provided context to the implementation. On a response, it carries implementation-provided context back to the caller. REST NAMESPACE ONLY Context entries are mapped to and from HTTP headers using the header. prefix: - On a request, any entry whose key starts with header. is sent as an HTTP request header with the prefix stripped. For example, the entry {\"header.Authorization\": \"Bearer abc\"} is sent as the request header Authorization: Bearer abc. - On a response, every HTTP response header is returned as an entry whose key is the header name prefixed with header.. For example, the response header x-request-id: abc123 is returned as the entry {\"header.x-request-id\": \"abc123\"}.
transaction_id: Option<String>Optional transaction identifier
properties: Option<HashMap<String, String>>Properties after the namespace is created. If the server does not support namespace properties, it should return null for this field. If namespace properties are supported, but none are set, it should return an empty object.
Implementations§
Source§impl CreateNamespaceResponse
impl CreateNamespaceResponse
pub fn new() -> CreateNamespaceResponse
Trait Implementations§
Source§impl Clone for CreateNamespaceResponse
impl Clone for CreateNamespaceResponse
Source§fn clone(&self) -> CreateNamespaceResponse
fn clone(&self) -> CreateNamespaceResponse
1.0.0 (const: unstable) · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more