⚠ This page is served via a proxy. Original site: https://github.com
This service does not collect credentials or authentication data.
Skip to content

tenant-specific deployment parameters #2379

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ecklie wants to merge 1 commit into
base: main
Choose a base branch
from
Open

tenant-specific deployment parameters #2379

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion guides/multitenancy/mtxs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1296,6 +1296,12 @@ The _SaasProvisioningService_ is a façade for the _DeploymentService_ to adapt
Requests are implicitly asynchronous when `status_callback` is set.
:::

##### Passing tenant-specific deployment parameters

Using the `"_"` section of the payload, you can pass deployment parameters for an individual tenant. The syntax is identical with the [static deployment configuration of the DeploymentService](#deployment-config).

In most cases, the requests are received from a third party, so the deployment parameters need to be added in [a handler implementation](#adding-custom-lifecycle-event-handlers) for service `cds.xt.SaasProvisioningService`.

##### Example Usage

<br>
Expand Down Expand Up @@ -1436,7 +1442,12 @@ Content-Type: application/json
{
"subscribedTenantId": "t1",
"subscribedSubdomain": "subdomain1",
"eventType": "CREATE"
"eventType": "CREATE",
"_": {
"hdi": {
...
}
}
}
```

Expand Down