[
https://jira.jboss.org/browse/TEIIDDES-578?page=com.atlassian.jira.plugin...
]
Barry LaFond updated TEIIDDES-578:
----------------------------------
Decided to clean up Data roles by simply removing stale Data Role "Permissions"
which are defined as permissions who's target/resource-name no longer exits due to
either removing a model from a VDB or by synchronizing a model that has changed in the
user's workspace.
In the case of removing a model, the permissions are simply removed. In the case of
"Synchronize" model or "Synchronize ALL" models action, a
"Note:" is included in the confirmation dialog (see attachement)
Changing the contents of a VDB does not refactor/clean-up or sync
with existing Data Roles in that VDB
------------------------------------------------------------------------------------------------------
Key: TEIIDDES-578
URL:
https://jira.jboss.org/browse/TEIIDDES-578
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Reporter: Barry LaFond
Assignee: Barry LaFond
Priority: Critical
Fix For: 7.1.1
Attachments: org.teiid.designer.roles.ui.patch, org.teiid.designer.vdb.ui.patch
The VDB Editor's Data Role framework is limited to creating Data Roles based on a
fixed set of Models in a VDB.
This does not take into account removing models or syncing (replacing) models with
changed/refactored contents.
We need to re-think how we can handle changes to the VDB contents. Do
"validiation"? Remove all permissions for changed/removed models?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira