Timeline for What is the rationale behind the microservice roles in SDL Web 8?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 26, 2016 at 16:46 | vote | accept | Dominic Cronin | ||
| May 13, 2016 at 16:21 | comment | added | Ashutosh | That does answer almost all the part of the question though, could relate now as to how these roles restrict certain operations that you don't want someone to do! | |
| May 13, 2016 at 12:09 | comment | added | Dominic Cronin | Yeah - that's the thing. There must be a reason why there are two distinct roles, so I've asked this question to try to get some insights into why? | |
| May 13, 2016 at 11:27 | comment | added | vinayknl | Sorry, missed that link. Agree that there is no specific detail about why and when to use implementer role, but as you can see in that page, the only difference between cd and implementer role is access to one of the end point in deployer (/deployer/isAlive). Other than that it is same as cd role. | |
| May 13, 2016 at 9:46 | comment | added | Dominic Cronin | I'd already read that page before I wrote my question. In fact, there's a link to it in my question. That's kind of the point, though - the documentation doesn't say anything about why you might need the implementer role. | |
| May 13, 2016 at 9:12 | comment | added | vinayknl | Implementer role is specific to CD side (for ex: can't publish). Recently updated answer to add link to the documentation page which describes this in detail. Can you please check it ? | |
| May 13, 2016 at 8:49 | comment | added | Dominic Cronin | So if I understand you correctly, the discovery-registration jar uses the provider role. I still don't get what the purpose of the implementer role is. Under what circumstances would you use it? | |
| May 13, 2016 at 8:16 | history | edited | vinayknl | CC BY-SA 3.0 |
added 146 characters in body
|
| May 10, 2016 at 7:24 | history | answered | vinayknl | CC BY-SA 3.0 |