Hi,
as part of the Fedora magazine migration (and likely commblog after), I would need someone to apply the attached patch, but this need to happen just after we resynced the WP instance (which take 1 or 2 minutes at worst). Can someone sync with me on how we can make that happen (like, block 1h of time or something in case we need to revert and something go wrong) ?
Alternatively, if I could be able to run groups/proxies.yml with rbac, this would permit to not block someone. <img alt="0001-Switch-to-the-new-host-for-Fedora-magazine.patch" src="/fedora-infrastructure/issue/raw/files/a8172866e113145d87fb3c90bc5efa758c53faf2c27053daf75248ae4ad0cfd9-0001-Switch-to-the-new-host-for-Fedora-magazine.patch" />
<img alt="0001-Switch-to-the-new-host-for-Fedora-magazine.patch" src="/fedora-infrastructure/issue/raw/files/b0a1dc0283079919bbde443ed0b742f7f3faf69f45c77837c44ab5d9daec059c-0001-Switch-to-the-new-host-for-Fedora-magazine.patch" />
I used the wrong hostname for the proxy, thanks to nb to have checked
I have added sysadmin-web to be able to run the proxies playbook. Note that this playbook takes a long time to run, so you may want to use a tag.
Is there anything else we can do for you? Or with those perms you are set?
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review)
Seems I can't:
$ sudo /bin/rbac-playbook -C groups/proxies.yml user misc is not authorized to run groups/proxies.yml
Checking
it should work now.
yep, it is working, I was able to run the playbook. I will close the ticket
Metadata Update from @misc: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.