You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Phil Zampino (JIRA)" <ji...@apache.org> on 2018/02/21 03:06:00 UTC

[jira] [Commented] (KNOX-1176) Provider Configuration Reference Isn't Updated If New Reference Is Invalid

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

Phil Zampino commented on KNOX-1176:
------------------------------------

Aslo, in the course of addressing this issue, noticed that support for descriptors for which no discovery details are specified was not completely correct. Knox must support descriptors in which all of the service endpoint URLs are . explicitly declared, and no discovery is desired/required to generate the associated topology. Therefore, some small changes were included in this commit to address this other issue.

> Provider Configuration Reference Isn't Updated If New Reference Is Invalid
> --------------------------------------------------------------------------
>
>                 Key: KNOX-1176
>                 URL: https://issues.apache.org/jira/browse/KNOX-1176
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 1.0.0
>            Reporter: Phil Zampino
>            Assignee: Phil Zampino
>            Priority: Minor
>             Fix For: 1.1.0
>
>
> If an existing simple descriptor is modified, such that its new provider configuration reference is invalid, the original reference relationship is (incorrectly) maintained. This relationship should be removed, whether the new reference is valid or not, because the descriptor no longer references the previously-referenced provider config. Maintaining this relationship prevents deletion of the previously-referenced provider configuration via the API (and UI), though manual deletion is still possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)