THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
public void contributeService( DeploymentContext context, Service service ) throws Exception {
List<ServiceParamDescriptor> params = null; // Default if null, otherwise map of per provider role map of name/value pairs.
ResourceDescriptor resource = context.addResource()
resource.role( "WEBHDFS" );
resource.pattern( "webhdfs/v1/**?**" );
context.contributeChain( service, resource, params );
}
|
...
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
public void contributeService( DeploymentContext context, Service service ) throws Exception {
UrlRewriteRulesDescriptor serviceRules = loadRulesFromClassPath();
UrlRewriteRulesDescriptor clusterRules = context.getDescriptor( "rewrite" );
clusterRules.addRules( serviceRules );
ResourceDescriptor resource;
List<ServiceParamDescriptor> params;
resource = context.getGatewayDescriptor().addResource();
resource.role( "WEBHDFS" );
resource.pattern( "webhdfs/v1/?**" );
resource.pattern( "webhdfs/v1/**?**" );
params = new ArrayList<ServiceParamDescriptor>();
params.add( resource.createParam().role( "rewrite", "request.url", "/webhdfs/namenode/inbound/path" );
params.add( resource.createParam().role( "rewrite", "response.headers", "/webhdfs/namenode/outbound/headers" );
context.contributeChain( service, resource, params );
resource = context.getGatewayDescriptor().addResource();
resourcenameNode.role( "WEBHDFS" );
resourcenameNode.pattern( "webhdfs/data/v1/**?**" );
params = new ArrayList<ServiceParamDescriptor>();
params.add( resource.createParam().role( "rewrite", "request.url", "/webhdfs/datanode/inbound/path" );
context.contributeChain( service, resource, params );
}
|
This is a sketch of how topology files would need to be extended to support the external chain definitions.
See comments within the XML for details.
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
<topology>
<gateway>
<provider>
<role>...</role>
<name>...</name>
<!-- Config for the provider. -->
<param><name>...</name><value>...</value></param>
</provider>
<!-- There can be multiple chain elements. -->
<!-- NOTE: There will be a "built-in" "default" chain definition. -->
<chain>
<name>...</name> <!-- Chains referenced by name by services. -->
<provider-ref> <!-- References a particular provider. -->
<role>...</role> <!--
<name>...</name>
<!-- Config for the provider to override those in the provider. -->
<param><name>...</name><value>...</value></param>
</provider-ref>
<provider-ref>...</provider-ref>
</chain>
<chain>...</chain>
</gateway>
<service>
<role>...</role>
<url>...</url>
<chain-ref>
<name>...</name>
<!-- Config for the provider to override those in the chain. -->
<param><role></role><name></name><value></value></param>
</chain-ref>
<!-- Config for the service. -->
<param><name></name><value></value></param>
</service>
</topology>
|
Details on the new elements within the topology are described below.
Path | Description |
|---|---|
topology/gateway/chain | TODO |
topology/gateway/chain/name | TODO |
topology/gateway/chain/provider-ref | TODO |
topology/gateway/chain/provider-ref/role | TODO |
topology/gateway/chain/provider-ref/name | TODO |
topology/gateway/chain/provider-ref/param | TODO |
topology/service/chain-ref | TODO |
topology/service/chain-ref/name | TODO |
topology/service/chain-ref/param | TODO |
topology/service/chain-ref/param/role | TODO |
topology/service/param | TODO |
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?
...