This will unify all the handlers to use first uppercase letter for
ansible-lint to stop complaining.
I went through all `notify:` occurrences and fixed them by running
```
set TEXT "text_to_replace"; set REPLACEMENT "replacement_text"; git grep
-rlz "$TEXT" . | xargs -0 sed -i "s/$TEXT/$REPLACEMENT/g"
```
Then I went through all the changes and removed the ones that wasn't
expected to be changed.
Fixes https://pagure.io/fedora-infrastructure/issue/12391
Signed-off-by: Michal Konecny <mkonecny@redhat.com>
This script is being moved to openshift.
The ssh keypair need to be recovered from ~_update_docs_trans/.ssh/id_rsa_docs_trans
and copied over /srv/private/ansible/files/docstranslation/id_rsa_docstrans_prod on batcave01.
Signed-off-by: Francois Andrieu <darknao@fedoraproject.org>
Right now we update translation files once a day at 22:00UTC.
So, it makes no sense to generate the translated docs more often than
once a day after that update. So, that cron moves to 23:00UTC.
The en cron can be once per hour, run it before sync.
Finally, adjust the docs-rsync script so it's actually idempotent,
and only transfers as much as it needs to.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Since sundries got reinstalled, there is a new ssh key, and
so we need to change the key on Pagure. Rather than bothering
someone each time that happen, it is better to just display
it so it can be added to Pagure.
Per ticket 8847, moving this cron job to 10pm will let it run and finish before the larger
and longer cron script runs to update the docs site. This will prevent overlap and get
updates out a day sooner in some cases.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Since that's run by cron, we have to accept the key.
Given that a MITM of pagure would just enable to intercept
nothing of value (we are using public keys, the data to be commited
can be regenerated trivially and would just concern translation),
disabling StrictHostKeyChecking for that user is IMHO not
a security risk.
Right now we are doing 3 rsyncs one at a time, but this prevents us
from deleting content that has disappeared from one of the first ones.
So, switch to doing one rsync with multiple sources and let it sort out
files that are now gone to be deleted in the target.
Fixes ticket 7334.
