@pmiazga, @Niedzielski and @phuedx will be the owners of the Proton PDF render. As such, they need to be in the deploy-service group. Note this constitutes a sudo request, since Scap ran by users in this group can start/stop services.
Description
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Add niedzielski, pmiazga and phuedx to deploy-service | operations/puppet | production | +2 -1 |
Event Timeline
@pmiazga, @Niedzielski and @phuedx, in order for this access to be granted, it needs to be approved by your respective managers. Please subscribe them and let them review the request.
Change 441379 had a related patch set uploaded (by Mobrovac; owner: Mobrovac):
[operations/puppet@production] Add niedzielski, pmiazga and phuedx to deploy-service
I approve this request for @Niedzielski and @pmiazga (I'm the Engineering Manager for Readers Web). @dr0ptp4kt will have to approve this request for me.
Just reviewing this as clinic duty this week, and this seems to be a deploy service, but doesn't list sudo rights in data.yaml. Does this include sudo rights deeper within the puppet code for this group, or does this group not act as any user other than the user's own?
The users in the deploy-service group can sudo service (start|stop|restart) * on the target nodes, so it essentially is a sudo request.
Thanks for feedback, duly noted and set in the proper column for SRE meeting review approval.
Change 441379 merged by Alexandros Kosiaris:
[operations/puppet@production] Add niedzielski, pmiazga and phuedx to deploy-service
I've emailed both @faidon and @mark for how to handle this, since it was merged without the meeting approval (at least as far as I can see.) This may have been discussed at the SRE offsite last week, which I did not attend, and it may have been approved there.
So with either @mark or @faidon's approval, we can leave this patchset merged/live and resolve this task.