THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Path | Description |
|---|---|
topology/gateway/chain TODO | This defines a new chain structure and configuration for use by services. |
topology/gateway/chain/name TODO | Specifies the name of the chain so that it can be referenced by services. |
topology/gateway/chain/provider-ref TODO | References a configured or default provider. May repeat. |
topology/gateway/chain/provider-ref/role TODO | A required role of a provider to be included in the chain. |
topology/gateway/chain/provider-ref/name TODO | An optional name of a specific provider for the given role. |
topology/gateway/chain/provider-ref/param | TODO Optional config parameters to augment the provider's configuration. |
topology/service/chain-ref TODO | Selects a specific chain to use for the service. May repeat. |
topology/service/chain-ref/name TODO | Specifies the name of the chain to use for the service. Default is "default" |
topology/service/chain-ref/param TODO | Optional parameters to augment the chain and provider configuration. |
topology/service/chain-ref/param/role TODO | A role name to disambiguate which provider the param is intended. |
topology/service/param TODO | Configuration parameters used by the service. May repeat. |
This shows the new method contributeChain() that would be added to the DeploymentContext interface.
The existing contributeFilter method would be deprecated.
This is actually a point worth further discussion.
Is there a use case where a service might want to define a chain this way?
...