[MGNLCI-18] Allow to configure User groups who can view and assign the import tasks, not only superuser Created: 15/Mar/18 Updated: 27/Apr/18 Resolved: 27/Apr/18 |
|
| Status: | Closed |
| Project: | Content Importer |
| Component/s: | None |
| Affects Version/s: | 1.0.1 |
| Fix Version/s: | 1.0.2 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Thanh Pham | Assignee: | Antonín Juran |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Release notes required: |
Yes
|
||||
| Documentation update required: |
Yes
|
||||
| Date of First Response: | |||||
| Sprint: | Kromeriz 143, Kromeriz 144 | ||||
| Story Points: | 5 | ||||
| Description |
|
Currently, when having a new/changed file in the content importer folder, the info.magnolia.content.observer.TaskCreatorWatcherCallback#addTask will create and send a task to users to review and import content. But only superuser is received the task: Task task = new Task(); task.setName("content"); task.setRequestor("superuser"); task.setStatus(Task.Status.Created); task.setActorIds(Lists.newArrayList("superuser")); task.setComment(changedFile.getName()); String repository = StringUtils.substringBefore(changedFile.getName(), "."); Map<String, Object> content = ImmutableMap.of( "repository", repository, "path", changedFile.getAbsolutePath(), "modificationDate", new Date()); task.setContent(content); tasksManager.addTask(task); We should get user groups in the configuration and set them to actorIds of the Task. Without this change the Content Importer cannot be used on Cloud and so there is no way to automate bootstrapping content on Cloud. |
| Comments |
| Comment by Ewa Snopczynska-Sienczylo [ 09/Apr/18 ] |
|
We disable superuser in cloud by default |
| Comment by Evzen Fochr [ 20/Apr/18 ] |
|
contentImporterTaskDefinition.getName() must be used TaskCreatorWatcherCallback line 131 |
| Comment by Antti Hietala [ 24/Apr/18 ] |
|
Reopened after sprint review. Please change the configuration property actorIds to users. While actorId is a technically correct term and it is used in the Task framework, it is unfamiliar to users. Let's use a more familiar term. |
| Comment by Roman Kovařík [ 24/Apr/18 ] |
|
ahietala For the record, "actors" is used in workflow definition |