In order to be able to deploy WDQS via scap3, we need to add to add members of wdqs-admins to deploy-service group. Also may be necessary to add @Gehel unless his other permissions also allow him to deploy services.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| admin: add wdqs-admins to deploy-service group | operations/puppet | production | +1 -1 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | MoritzMuehlenhoff | T164780 Sunset our use of Salt | |||
| Resolved | thcipriani | T129290 [keyresult] Migrate remaining trebuchet deployed services | |||
| Resolved | Smalyshev | T129144 Deploy wdqs with scap3 | |||
| Resolved | Dzahn | T138628 Add wdqs-admins to deploy-services group |
Event Timeline
Comment Actions
Change 296658 had a related patch set uploaded (by Dzahn):
admin: add wdqs-admins to deploy-service group
Comment Actions
I think there's going to be a lot more of these as more services are converted to use scap. I presume members of this group used to own the trebuchet deployment process? If so let's Just Do It.
Comment Actions
Change 296658 merged by Filippo Giunchedi:
admin: add wdqs-admins to deploy-service group
Comment Actions
I don't think gehel needs to be added because his existing permissions already allow him everything. Unless we want to do it for more symbolic reasons or to make things more obvious to human readers.
Comment Actions
[tin:~] $ id smalyshev uid=10977(smalyshev) gid=500(wikidev) groups=500(wikidev),755(wdqs-admins),763(deploy-service) [tin:~] $ id hoo uid=2133(hoo) gid=500(wikidev) groups=500(wikidev),755(wdqs-admins),763(deploy-service),705(deployment) [tin:~] $ id jzerebecki uid=2844(jzerebecki) gid=500(wikidev) groups=500(wikidev),755(wdqs-admins),763(deploy-service),705(deployment)