apis
/
bndry.workflows.tenantprovisioning.v1alpha.TenantProvisioning

Download OpenAPI description
openapi.json
openapi.yaml
Languages
Servers
Mock server
https://docs.bndry.net/_mock/apis/openapi/

Form Definitions

Operations

Workspaces

Operations

Entities

Operations

Tenants

Operations

bndry.workflows.tenantprovisioning.v1alpha.TenantProvisioning

Operations

ProvisionTenant

Request

Headers
Connect-Protocol-Versionnumber(Connect-Protocol-Version)required

Define the version of the Connect protocol

Value1
Value 1
Connect-Timeout-Msnumber(Connect-Timeout-Ms)

Define the timeout, in ms

Bodyapplication/jsonrequired
displayNamestring(display_name)
curl -i -X POST \
  https://docs.bndry.net/_mock/apis/openapi/api/bndry.workflows.tenantprovisioning.v1alpha.TenantProvisioning/ProvisionTenant \
  -H 'Connect-Protocol-Version: 1' \
  -H 'Connect-Timeout-Ms: 0' \
  -H 'Content-Type: application/json' \
  -d '{
    "displayName": "string"
  }'

Responses

Success

Bodyapplication/json
object(ProvisionTenantResponse)
Response
application/json
{}

CreateTenant

Request

Headers
Connect-Protocol-Versionnumber(Connect-Protocol-Version)required

Define the version of the Connect protocol

Value1
Value 1
Connect-Timeout-Msnumber(Connect-Timeout-Ms)

Define the timeout, in ms

Bodyapplication/jsonrequired
resourceIdstring(resource_id)
displayNamestring(display_name)
createTimestring(date-time)(google.protobuf.Timestamp)

A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one.

All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap second table is needed for interpretation, using a 24-hour linear smear.

The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from RFC 3339 date strings.

Examples

Example 1: Compute Timestamp from POSIX time().

Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0);

Example 2: Compute Timestamp from POSIX gettimeofday().

struct timeval tv; gettimeofday(&tv, NULL);

Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000);

Example 3: Compute Timestamp from Win32 GetSystemTimeAsFileTime().

FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime;

// A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));

Example 4: Compute Timestamp from Java System.currentTimeMillis().

long millis = System.currentTimeMillis();

Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build();

Example 5: Compute Timestamp from Java Instant.now().

Instant now = Instant.now();

Timestamp timestamp = Timestamp.newBuilder().setSeconds(now.getEpochSecond()) .setNanos(now.getNano()).build();

Example 6: Compute Timestamp from current time in Python.

timestamp = Timestamp() timestamp.GetCurrentTime()

JSON Mapping

In JSON format, the Timestamp type is encoded as a string in the RFC 3339 format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset).

For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017.

In JavaScript, one can convert a Date object to this format using the standard toISOString() method. In Python, a standard datetime.datetime object can be converted to this format using strftime with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use the Joda Time's ISODateTimeFormat.dateTime() to obtain a formatter capable of generating timestamps in this format.

curl -i -X POST \
  https://docs.bndry.net/_mock/apis/openapi/api/bndry.workflows.tenantprovisioning.v1alpha.TenantProvisioning/CreateTenant \
  -H 'Connect-Protocol-Version: 1' \
  -H 'Connect-Timeout-Ms: 0' \
  -H 'Content-Type: application/json' \
  -d '{
    "resourceId": "string",
    "displayName": "string",
    "createTime": "2019-08-24T14:15:22Z"
  }'

Responses

Success

Bodyapplication/json
resourceIdstring(resource_id)
displayNamestring(display_name)
createTimestring(date-time)(google.protobuf.Timestamp)

A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one.

All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap second table is needed for interpretation, using a 24-hour linear smear.

The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from RFC 3339 date strings.

Examples

Example 1: Compute Timestamp from POSIX time().

Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0);

Example 2: Compute Timestamp from POSIX gettimeofday().

struct timeval tv; gettimeofday(&tv, NULL);

Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000);

Example 3: Compute Timestamp from Win32 GetSystemTimeAsFileTime().

FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime;

// A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));

Example 4: Compute Timestamp from Java System.currentTimeMillis().

long millis = System.currentTimeMillis();

Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build();

Example 5: Compute Timestamp from Java Instant.now().

Instant now = Instant.now();

Timestamp timestamp = Timestamp.newBuilder().setSeconds(now.getEpochSecond()) .setNanos(now.getNano()).build();

Example 6: Compute Timestamp from current time in Python.

timestamp = Timestamp() timestamp.GetCurrentTime()

JSON Mapping

In JSON format, the Timestamp type is encoded as a string in the RFC 3339 format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset).

For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017.

In JavaScript, one can convert a Date object to this format using the standard toISOString() method. In Python, a standard datetime.datetime object can be converted to this format using strftime with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use the Joda Time's ISODateTimeFormat.dateTime() to obtain a formatter capable of generating timestamps in this format.

updateTimestring(date-time)(google.protobuf.Timestamp)

A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one.

All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap second table is needed for interpretation, using a 24-hour linear smear.

The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from RFC 3339 date strings.

Examples

Example 1: Compute Timestamp from POSIX time().

Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0);

Example 2: Compute Timestamp from POSIX gettimeofday().

struct timeval tv; gettimeofday(&tv, NULL);

Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000);

Example 3: Compute Timestamp from Win32 GetSystemTimeAsFileTime().

FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime;

// A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));

Example 4: Compute Timestamp from Java System.currentTimeMillis().

long millis = System.currentTimeMillis();

Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build();

Example 5: Compute Timestamp from Java Instant.now().

Instant now = Instant.now();

Timestamp timestamp = Timestamp.newBuilder().setSeconds(now.getEpochSecond()) .setNanos(now.getNano()).build();

Example 6: Compute Timestamp from current time in Python.

timestamp = Timestamp() timestamp.GetCurrentTime()

JSON Mapping

In JSON format, the Timestamp type is encoded as a string in the RFC 3339 format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset).

For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017.

In JavaScript, one can convert a Date object to this format using the standard toISOString() method. In Python, a standard datetime.datetime object can be converted to this format using strftime with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use the Joda Time's ISODateTimeFormat.dateTime() to obtain a formatter capable of generating timestamps in this format.

idstring(id)
Response
application/json
{
  "resourceId": "string",
  "displayName": "string",
  "createTime": "2019-08-24T14:15:22Z",
  "updateTime": "2019-08-24T14:15:22Z",
  "id": "string"
}

CreateKeycloakOrganization

Request

Headers
Connect-Protocol-Versionnumber(Connect-Protocol-Version)required

Define the version of the Connect protocol

Value1
Value 1
Connect-Timeout-Msnumber(Connect-Timeout-Ms)

Define the timeout, in ms

Bodyapplication/jsonrequired
realmstring(realm)
tenantobject(bndry.workflows.tenantprovisioning.v1alpha.Tenant)
curl -i -X POST \
  https://docs.bndry.net/_mock/apis/openapi/api/bndry.workflows.tenantprovisioning.v1alpha.TenantProvisioning/CreateKeycloakOrganization \
  -H 'Connect-Protocol-Version: 1' \
  -H 'Connect-Timeout-Ms: 0' \
  -H 'Content-Type: application/json' \
  -d '{
    "realm": "string",
    "tenant": {
      "resourceId": "string",
      "displayName": "string",
      "createTime": "2019-08-24T14:15:22Z",
      "updateTime": "2019-08-24T14:15:22Z",
      "id": "string"
    }
  }'

Responses

Success

Bodyapplication/json
organizationIdstring(organization_id)
Response
application/json
{
  "organizationId": "string"
}

CreateKeycloakDefaultOrganizationRoles

Request

Headers
Connect-Protocol-Versionnumber(Connect-Protocol-Version)required

Define the version of the Connect protocol

Value1
Value 1
Connect-Timeout-Msnumber(Connect-Timeout-Ms)

Define the timeout, in ms

Bodyapplication/jsonrequired
realmstring(realm)
organizationIdstring(organization_id)
curl -i -X POST \
  https://docs.bndry.net/_mock/apis/openapi/api/bndry.workflows.tenantprovisioning.v1alpha.TenantProvisioning/CreateKeycloakDefaultOrganizationRoles \
  -H 'Connect-Protocol-Version: 1' \
  -H 'Connect-Timeout-Ms: 0' \
  -H 'Content-Type: application/json' \
  -d '{
    "realm": "string",
    "organizationId": "string"
  }'

Responses

Success

Bodyapplication/json
object(google.protobuf.Empty)

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance:

service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }

Response
application/json
{}

SetTenantKeycloakOrganizationId

Request

Headers
Connect-Protocol-Versionnumber(Connect-Protocol-Version)required

Define the version of the Connect protocol

Value1
Value 1
Connect-Timeout-Msnumber(Connect-Timeout-Ms)

Define the timeout, in ms

Bodyapplication/jsonrequired
tenantobject(bndry.workflows.tenantprovisioning.v1alpha.Tenant)
organizationIdstring(organization_id)
curl -i -X POST \
  https://docs.bndry.net/_mock/apis/openapi/api/bndry.workflows.tenantprovisioning.v1alpha.TenantProvisioning/SetTenantKeycloakOrganizationId \
  -H 'Connect-Protocol-Version: 1' \
  -H 'Connect-Timeout-Ms: 0' \
  -H 'Content-Type: application/json' \
  -d '{
    "tenant": {
      "resourceId": "string",
      "displayName": "string",
      "createTime": "2019-08-24T14:15:22Z",
      "updateTime": "2019-08-24T14:15:22Z",
      "id": "string"
    },
    "organizationId": "string"
  }'

Responses

Success

Bodyapplication/json
object(google.protobuf.Empty)

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance:

service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }

Response
application/json
{}

CreateTemporalNamespace

Request

Headers
Connect-Protocol-Versionnumber(Connect-Protocol-Version)required

Define the version of the Connect protocol

Value1
Value 1
Connect-Timeout-Msnumber(Connect-Timeout-Ms)

Define the timeout, in ms

Bodyapplication/jsonrequired
tenantobject(bndry.workflows.tenantprovisioning.v1alpha.Tenant)
curl -i -X POST \
  https://docs.bndry.net/_mock/apis/openapi/api/bndry.workflows.tenantprovisioning.v1alpha.TenantProvisioning/CreateTemporalNamespace \
  -H 'Connect-Protocol-Version: 1' \
  -H 'Connect-Timeout-Ms: 0' \
  -H 'Content-Type: application/json' \
  -d '{
    "tenant": {
      "resourceId": "string",
      "displayName": "string",
      "createTime": "2019-08-24T14:15:22Z",
      "updateTime": "2019-08-24T14:15:22Z",
      "id": "string"
    }
  }'

Responses

Success

Bodyapplication/json
temporalNamespacestring(temporal_namespace)
Response
application/json
{
  "temporalNamespace": "string"
}

SetTenantTemporalNamespace

Request

Headers
Connect-Protocol-Versionnumber(Connect-Protocol-Version)required

Define the version of the Connect protocol

Value1
Value 1
Connect-Timeout-Msnumber(Connect-Timeout-Ms)

Define the timeout, in ms

Bodyapplication/jsonrequired
tenantobject(bndry.workflows.tenantprovisioning.v1alpha.Tenant)
temporalNamespacestring(temporal_namespace)
curl -i -X POST \
  https://docs.bndry.net/_mock/apis/openapi/api/bndry.workflows.tenantprovisioning.v1alpha.TenantProvisioning/SetTenantTemporalNamespace \
  -H 'Connect-Protocol-Version: 1' \
  -H 'Connect-Timeout-Ms: 0' \
  -H 'Content-Type: application/json' \
  -d '{
    "tenant": {
      "resourceId": "string",
      "displayName": "string",
      "createTime": "2019-08-24T14:15:22Z",
      "updateTime": "2019-08-24T14:15:22Z",
      "id": "string"
    },
    "temporalNamespace": "string"
  }'

Responses

Success

Bodyapplication/json
object(google.protobuf.Empty)

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance:

service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }

Response
application/json
{}

SetExampleEntities

Request

Headers
Connect-Protocol-Versionnumber(Connect-Protocol-Version)required

Define the version of the Connect protocol

Value1
Value 1
Connect-Timeout-Msnumber(Connect-Timeout-Ms)

Define the timeout, in ms

Bodyapplication/jsonrequired
tenantobject(bndry.workflows.tenantprovisioning.v1alpha.Tenant)
curl -i -X POST \
  https://docs.bndry.net/_mock/apis/openapi/api/bndry.workflows.tenantprovisioning.v1alpha.TenantProvisioning/SetExampleEntities \
  -H 'Connect-Protocol-Version: 1' \
  -H 'Connect-Timeout-Ms: 0' \
  -H 'Content-Type: application/json' \
  -d '{
    "tenant": {
      "resourceId": "string",
      "displayName": "string",
      "createTime": "2019-08-24T14:15:22Z",
      "updateTime": "2019-08-24T14:15:22Z",
      "id": "string"
    }
  }'

Responses

Success

Bodyapplication/json
object(google.protobuf.Empty)

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance:

service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }

Response
application/json
{}

SeedDefaultForms

Request

Headers
Connect-Protocol-Versionnumber(Connect-Protocol-Version)required

Define the version of the Connect protocol

Value1
Value 1
Connect-Timeout-Msnumber(Connect-Timeout-Ms)

Define the timeout, in ms

Bodyapplication/jsonrequired
tenantobject(bndry.workflows.tenantprovisioning.v1alpha.Tenant)
curl -i -X POST \
  https://docs.bndry.net/_mock/apis/openapi/api/bndry.workflows.tenantprovisioning.v1alpha.TenantProvisioning/SeedDefaultForms \
  -H 'Connect-Protocol-Version: 1' \
  -H 'Connect-Timeout-Ms: 0' \
  -H 'Content-Type: application/json' \
  -d '{
    "tenant": {
      "resourceId": "string",
      "displayName": "string",
      "createTime": "2019-08-24T14:15:22Z",
      "updateTime": "2019-08-24T14:15:22Z",
      "id": "string"
    }
  }'

Responses

Success

Bodyapplication/json
object(google.protobuf.Empty)

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance:

service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }

Response
application/json
{}

CreateKmsKey

Request

Headers
Connect-Protocol-Versionnumber(Connect-Protocol-Version)required

Define the version of the Connect protocol

Value1
Value 1
Connect-Timeout-Msnumber(Connect-Timeout-Ms)

Define the timeout, in ms

Bodyapplication/jsonrequired
tenantobject(bndry.workflows.tenantprovisioning.v1alpha.Tenant)
curl -i -X POST \
  https://docs.bndry.net/_mock/apis/openapi/api/bndry.workflows.tenantprovisioning.v1alpha.TenantProvisioning/CreateKmsKey \
  -H 'Connect-Protocol-Version: 1' \
  -H 'Connect-Timeout-Ms: 0' \
  -H 'Content-Type: application/json' \
  -d '{
    "tenant": {
      "resourceId": "string",
      "displayName": "string",
      "createTime": "2019-08-24T14:15:22Z",
      "updateTime": "2019-08-24T14:15:22Z",
      "id": "string"
    }
  }'

Responses

Success

Bodyapplication/json
kmsKeyIdstring(kms_key_id)
Response
application/json
{
  "kmsKeyId": "string"
}

SetTenantKmsKey

Request

Headers
Connect-Protocol-Versionnumber(Connect-Protocol-Version)required

Define the version of the Connect protocol

Value1
Value 1
Connect-Timeout-Msnumber(Connect-Timeout-Ms)

Define the timeout, in ms

Bodyapplication/jsonrequired
tenantobject(bndry.workflows.tenantprovisioning.v1alpha.Tenant)
kmsKeyIdstring(kms_key_id)
curl -i -X POST \
  https://docs.bndry.net/_mock/apis/openapi/api/bndry.workflows.tenantprovisioning.v1alpha.TenantProvisioning/SetTenantKmsKey \
  -H 'Connect-Protocol-Version: 1' \
  -H 'Connect-Timeout-Ms: 0' \
  -H 'Content-Type: application/json' \
  -d '{
    "tenant": {
      "resourceId": "string",
      "displayName": "string",
      "createTime": "2019-08-24T14:15:22Z",
      "updateTime": "2019-08-24T14:15:22Z",
      "id": "string"
    },
    "kmsKeyId": "string"
  }'

Responses

Success

Bodyapplication/json
object(google.protobuf.Empty)

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance:

service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }

Response
application/json
{}

CreateBucket

Request

Headers
Connect-Protocol-Versionnumber(Connect-Protocol-Version)required

Define the version of the Connect protocol

Value1
Value 1
Connect-Timeout-Msnumber(Connect-Timeout-Ms)

Define the timeout, in ms

Bodyapplication/jsonrequired
tenantobject(bndry.workflows.tenantprovisioning.v1alpha.Tenant)
kmsKeyIdstring(kms_key_id)
curl -i -X POST \
  https://docs.bndry.net/_mock/apis/openapi/api/bndry.workflows.tenantprovisioning.v1alpha.TenantProvisioning/CreateBucket \
  -H 'Connect-Protocol-Version: 1' \
  -H 'Connect-Timeout-Ms: 0' \
  -H 'Content-Type: application/json' \
  -d '{
    "tenant": {
      "resourceId": "string",
      "displayName": "string",
      "createTime": "2019-08-24T14:15:22Z",
      "updateTime": "2019-08-24T14:15:22Z",
      "id": "string"
    },
    "kmsKeyId": "string"
  }'

Responses

Success

Bodyapplication/json
bucketNamestring(bucket_name)
Response
application/json
{
  "bucketName": "string"
}

SetTenantBucket

Request

Headers
Connect-Protocol-Versionnumber(Connect-Protocol-Version)required

Define the version of the Connect protocol

Value1
Value 1
Connect-Timeout-Msnumber(Connect-Timeout-Ms)

Define the timeout, in ms

Bodyapplication/jsonrequired
tenantobject(bndry.workflows.tenantprovisioning.v1alpha.Tenant)
bucketNamestring(bucket_name)
curl -i -X POST \
  https://docs.bndry.net/_mock/apis/openapi/api/bndry.workflows.tenantprovisioning.v1alpha.TenantProvisioning/SetTenantBucket \
  -H 'Connect-Protocol-Version: 1' \
  -H 'Connect-Timeout-Ms: 0' \
  -H 'Content-Type: application/json' \
  -d '{
    "tenant": {
      "resourceId": "string",
      "displayName": "string",
      "createTime": "2019-08-24T14:15:22Z",
      "updateTime": "2019-08-24T14:15:22Z",
      "id": "string"
    },
    "bucketName": "string"
  }'

Responses

Success

Bodyapplication/json
object(google.protobuf.Empty)

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance:

service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }

Response
application/json
{}