You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Kevin Minder (JIRA)" <ji...@apache.org> on 2015/04/20 20:27:59 UTC

[jira] [Commented] (KNOX-176) Per Service overrides of Provider parameters

    [ https://issues.apache.org/jira/browse/KNOX-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503350#comment-14503350 ] 

Kevin Minder commented on KNOX-176:
-----------------------------------

This is supported although I could not determine exactly which commit added this support.  Contributors however have to explicitly support reading the properties during deployment.  At present (i.e. 0.6.0) only the DispatchDeploymentContributor seems to be utilizing this.

> Per Service overrides of Provider parameters
> --------------------------------------------
>
>                 Key: KNOX-176
>                 URL: https://issues.apache.org/jira/browse/KNOX-176
>             Project: Apache Knox
>          Issue Type: Improvement
>          Components: Server
>    Affects Versions: 0.3.0
>            Reporter: Kevin Minder
>            Assignee: Kevin Minder
>             Fix For: 0.5.0
>
>
> Within the topology file it should be possible to override some of the provider params at the service level.  The complicating factor is figuring how what filters should be setup with the service's params.  Should the param names be prefixed with a provider's role and name?
> <topology>
>   <gateway>
>     <provider>
>       <role>X</role?
>       <param><name>Y</name><value>Z</value></param>
>     </provider>
>   </gateway>
>   <service>
>     <role>A</role>
>     <param><name>Y</name><value>Z</value></param>
>   </service>
> </topology>



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)