[
https://issues.apache.org/jira/browse/SYNCOPE-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-229:
-------------------------------------------
Description:
Use case: a new version of a connector bundle is released.
It should be possible then to install this new connector bundle in Syncope,
then change the bundle version in the corresponding ConnInstance(s) (currently
not allowed). All this by taking care of merging existing ConnInstance
configuration.
[1] http://syncope-user.1051894.n5.nabble.com/csvdir-connector-td5706733.html
was:
This is currently not possible: the connector instance can only be selected
during external resource creation and cannot be changed any more.
This has been done for the sake of safety, since the schema mapping is
completely dependent on the underlying connector instance; from the other side,
in this way it is hard, for example, to manage connector bundle upgrades (see
[1]).
It would be nice then to allow this kind of change, even at the price of
scratching out the existing schema mapping of the resource being updated.
[1] http://syncope-user.1051894.n5.nabble.com/csvdir-connector-td5706733.html
> Allow to change the bundle version associated to an existing connector
> instance
> -------------------------------------------------------------------------------
>
> Key: SYNCOPE-229
> URL: https://issues.apache.org/jira/browse/SYNCOPE-229
> Project: Syncope
> Issue Type: Improvement
> Reporter: Francesco Chicchiriccò
> Assignee: Marco Di Sabatino Di Diodoro
> Fix For: 1.1.0
>
>
> Use case: a new version of a connector bundle is released.
> It should be possible then to install this new connector bundle in Syncope,
> then change the bundle version in the corresponding ConnInstance(s)
> (currently not allowed). All this by taking care of merging existing
> ConnInstance configuration.
> [1] http://syncope-user.1051894.n5.nabble.com/csvdir-connector-td5706733.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
