[
https://issues.apache.org/jira/browse/ARIES-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18080439#comment-18080439
]
ASF subversion and git services commented on ARIES-2214:
--------------------------------------------------------
Commit d7b7d6b42c05c8f1dc9cd8106a45d5a12b0cee6c in aries-rsa's branch
refs/heads/master from Amichai Rothman
[ https://gitbox.apache.org/repos/asf?p=aries-rsa.git;h=d7b7d6b4 ]
ARIES-2214 Fix provider config type handling
> Fix provider config type handling
> ---------------------------------
>
> Key: ARIES-2214
> URL: https://issues.apache.org/jira/browse/ARIES-2214
> Project: Aries
> Issue Type: Bug
> Components: Remote Service Admin
> Affects Versions: rsa-1.16.1
> Reporter: Amichai Rothman
> Priority: Major
>
> The handling of configuration type properties (i.e. selecting which
> distribution provider to use and which types of distribution implementation
> it will use) are not exactly according to spec:
> - a distribution provider may support multiple configuration types, and a
> service may explicitly specify which configuration types it wants to use for
> export in
> SERVICE_EXPORTED_CONFIGS - we need to use the intersection of both of them to
> determine which configuration types to try exporting with
> - if SERVICE_EXPORTED_CONFIGS is empty, we need to pick one of the supported
> types
> - the created endpoint properties should have a SERVICE_EXPORTED_CONFIGS
> property set to the configuration type that was used for that particual
> endpoint (and any aliases it may have)
> - there is some related refactoring that could be done to clarify how this
> mechanism works
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
