documentation update WRT underscore to dash change in arguments

Fixes: fedora-copr#1099

Author: hrnciar

beaker-tests/Regression/frontend/setup.sh

@@ -32,6 +32,6 @@ sudo tar -xf /vagrant/frontend-files.tar -C /
 echo "*:*:coprdb:copr-fe:coprpass" > ~/.pgpass
 chmod 600 ~/.pgpass
 psql -U copr-fe coprdb < /setup-user.sql
-sudo copr-frontend create_chroot fedora-24-x86_64
+sudo copr-frontend create-chroot fedora-24-x86_64
 ' frontend
 rm $COPRROOTDIR/frontend-files.tar

copr-setup.txt

@@ -69,9 +69,9 @@ Frontend:
 - cd /usr/share/copr/coprs_frontend
 - configure DB first - see DB section below
 # for develop setup do:
-COPR_CONFIG=/etc/copr/copr_devel.conf ./manage.py create_db --alembic alembic.ini
+COPR_CONFIG=/etc/copr/copr_devel.conf ./manage.py create-db --alembic alembic.ini
 # for production setup do:
-./manage.py create_db  --alembic alembic.ini
+./manage.py create-db  --alembic alembic.ini
 
 - for developing you can run:
   ./manage.py runserver -t <FQDN>
@@ -80,7 +80,7 @@ COPR_CONFIG=/etc/copr/copr_devel.conf ./manage.py create_db --alembic alembic.in
 - for production is used ProductionConfig from coprs_frontend/coprs/config.py
 
 - Add chroots. E.g:
- su - copr-fe -c './manage.py create_chroot fedora-18-x86_64 fedora-18-i386'
+ su - copr-fe -c './manage.py create-chroot fedora-18-x86_64 fedora-18-i386'
 
 
 DB config
@@ -97,7 +97,7 @@ SQLite
 This will use sqlite db file in /var/lib/copr/data/copr.db (manage.py will create that file)
 - Note that you have to either create db as copr-fe user or you have to run:
   chown copr-fe:copr-fe /var/lib/copr/data/copr.db
-  after you run "./manage.py create_db --alembic alembic.ini"
+  after you run "./manage.py create-db --alembic alembic.ini"
 
 PostgreSQL
 ~~~~~~~~~~
@@ -128,7 +128,7 @@ PGPASSWORD=coprpass psql -a -U copr-fe coprdb
 PGPASSWORD=coprpass psql -a -h localhost -U copr-fe coprdb
 
 Then run:
-  "./manage.py create_db --alembic alembic.ini"
+  "./manage.py create-db --alembic alembic.ini"
 
 Upgrade
 =======
@@ -141,7 +141,7 @@ Make yourself admin
 
 Run:
   cd /usr/share/copr/coprs_frontend/
-  ./manage.py alter_user --admin msuchy
+  ./manage.py alter-user --admin msuchy
 
 Then navigate to:
   http://your.copr.fqdn/admin
@@ -151,11 +151,11 @@ Add new chroot
 
 First create new chroots:
 
-    python manage.py create_chroot fedora-24-i386 fedora-24-x86_64
+    python manage.py create-chroot fedora-24-i386 fedora-24-x86_64
 
 And then copy data from rawhide into them:
 
-    python manage.py rawhide_to_release fedora-rawhide-i386 fedora-24-i386
+    python manage.py rawhide-to-release fedora-rawhide-i386 fedora-24-i386
     # similarly for fedora-24-x86_64
 
 DEBUGGING

doc/how_to_delete_outdated_chroots.rst

@@ -24,7 +24,7 @@ To briefly summarize it, first, it is required to mark a chroot as EOL (aka outd
 
 ::
 
-    copr-frontend alter_chroot --action eol fedora-25-x86_64
+    copr-frontend alter-chroot --action eol fedora-25-x86_64
 
 It doesn't matter whether the chroot is currently activated or deactivated, using ``--action eol``
 always deactivates it. More importantly, for every related ``CoprChroot`` it generates a ``delete_after`` timestamp
@@ -40,24 +40,24 @@ project owners are going to be notified, but rather all project admins.
 
 ::
 
-    copr-frontend notify_outdated_chroots --dry-run
+    copr-frontend notify-outdated-chroots --dry-run
 
 When working on a non-production instance and wanting to really send the emails, filter the recipients to just yourself
 or team members. Any *real* users shouldn't be contacted from devel instances!
 
 ::
 
-    copr-frontend notify_outdated_chroots --dry-run -e [email protected]
+    copr-frontend notify-outdated-chroots --dry-run -e [email protected]
 
 If this command prints that it would notify just the expected people (which were specified with the ``-e`` parameter),
 then it is safe to run it without ``--dry-run`` parameter.
 
 ::
 
-    copr-frontend notify_outdated_chroots -e [email protected]
+    copr-frontend notify-outdated-chroots -e [email protected]
 
 
-When the notification about a particular copr chroot is sent and then the ``notify_outdated_chroots`` command
+When the notification about a particular copr chroot is sent and then the ``notify-outdated-chroots`` command
 is executed again, it will not send the notification for the second time. It is designed to be daily executed via Cron
 and it needs to avoid spamming the people over and over again. Therefore when a notification is sent, a timestamp when
 to send a next one is stored to the ``delete_notify`` column. In a case that this logic needs to be suppressed,
@@ -72,18 +72,18 @@ all the chroots for which this applies, use this command.
 
 ::
 
-    copr-frontend delete_outdated_chroots --dry-run
+    copr-frontend delete-outdated-chroots --dry-run
 
 To really delete them (i.e. creating an action which will delete the chroot directory on the backend),
 run the command without ``--dry-run`` parameter.
 
 ::
 
-    copr-frontend delete_outdated_chroots
+    copr-frontend delete-outdated-chroots
 
 When deleting the chroot (creating an action to delete the data on the backend), the ``delete_after``
-and ``delete_notify`` columns are set to NULL and therefore ``notify_outdated_chroots``
-and ``delete_outdated_chroots`` commands don't see the chroot anymore.
+and ``delete_notify`` columns are set to NULL and therefore ``notify-outdated-chroots``
+and ``delete-outdated-chroots`` commands don't see the chroot anymore.
 
 
 Automatization

doc/how_to_manage_chroots.rst

@@ -14,11 +14,11 @@ Chroots can be easily managed with these few commands.
 
 ::
 
-    copr-frontend create_chroot <name>
-    copr-frontend alter_chroot --action activate <name>
-    copr-frontend alter_chroot --action deactivate <name>
-    copr-frontend branch_fedora <new-branched-version>
-    copr-frontend rawhide_to_release <rawhide-chroot> <newly-created-chroot>
+    copr-frontend create-chroot <name>
+    copr-frontend alter-chroot --action activate <name>
+    copr-frontend alter-chroot --action deactivate <name>
+    copr-frontend branch-fedora <new-branched-version>
+    copr-frontend rawhide-to-release <rawhide-chroot> <newly-created-chroot>
 
 However, `enablement process upon Fedora branching <#branching-process>`_ and also
 `chroot deactivation when Fedora reaches it's EOL phase <#eol-deactivation-process>`_, are not that simple.
@@ -36,20 +36,20 @@ chroot.
 So **immediately** after Fedora branching (for exmaple to version **31**), you
 want to do this (the command takes a very long time, be prepared)::
 
-    copr-frontend branch_fedora 31
+    copr-frontend branch-fedora 31
 
 This command creates ``fedora-31-*`` chroots from corresponding
 ``fedora-rawhide-*`` chroots, and it also copies (duplicates/forks) latest
 successful rawhide package builds into the new chroots.  This can be done
 manually for each architecture by::
 
-    copr-frontend create_chroot fedora-31-x86_64 --deactivated
-    copr-frontend rawhide_to_release fedora-rawhide-x86_64 fedora-31-x86_64
+    copr-frontend create-chroot fedora-31-x86_64 --deactivated
+    copr-frontend rawhide-to-release fedora-rawhide-x86_64 fedora-31-x86_64
 
 From the manual steps you can see that the new chroots are **deactivated** at
 the beginning.
 
-It's important to do ``rawhide_to_release`` as soon as possible, because right
+It's important to do ``rawhide-to-release`` as soon as possible, because right
 after branching action - Fedora Rawhide starts to live it's own separate life -
 and the builds in Rawhide become more and more incompatible with the branched
 Fedora.  So - if we copied the packages later - the branched chroot in copr
@@ -67,11 +67,11 @@ and in which version of the :code:`mock-core-configs` package they were added. I
 on builders, you should keep the chroots deactivated for now and continue later.
 
 But the sooner we can enable the new chroots, the better -- all the builds that
-happened in the time window between ``rawhide_to_release`` and chroot enablement
+happened in the time window between ``rawhide-to-release`` and chroot enablement
 will be missed in the branched chroot later (users will have to rebuild them
 manually).  So as soon as it is possible, do::
 
-    copr-frontend alter_chroot --action activate \
+    copr-frontend alter-chroot --action activate \
         fedora-31-x86_64 fedora-31-i386 fedora-31-ppc64le fedora-31-aarch64
 
 When everything is done, `send an information email to a mailing list <#mailing-lists>`_.
@@ -88,7 +88,7 @@ comfortably deal with it. It can be done like this
 
 ::
 
-    copr-frontend alter_chroot --action eol fedora-25-x86_64 fedora-25-i386 fedora-25-ppc64le
+    copr-frontend alter-chroot --action eol fedora-25-x86_64 fedora-25-i386 fedora-25-ppc64le
 
 After running such command, no data are going to be removed. All repositories for the chroot are preserved. It is just
 disabled and users can't build new packages in it anymore.

docker/frontend/files/usr/bin/run.sh

@@ -7,8 +7,8 @@ export LANG=en_US.UTF-8
 chown -R copr-fe:copr-fe /var/log/copr-frontend
 chown -R copr-fe:copr-fe /usr/share/copr
 
-cd /usr/share/copr/coprs_frontend/ && sudo -u copr-fe copr-frontend create_db --alembic alembic.ini
-sudo -u copr-fe copr-frontend create_chroot \
+cd /usr/share/copr/coprs_frontend/ && sudo -u copr-fe copr-frontend create-db --alembic alembic.ini
+sudo -u copr-fe copr-frontend create-chroot \
     $(ls /etc/mock/{fedora,epel}-*-{i386,x86_64}.cfg |xargs -I{} -n1 basename {} .cfg)
 
 # selinux: make data dir writeable for httpd

frontend/conf/cron.daily/copr-frontend

@@ -4,6 +4,6 @@
 # daily.  Don't edit this file manually, it is automatically updated with
 # copr-frontend.rpm.
 
-runuser -c '/usr/share/copr/coprs_frontend/manage.py vacuum_graphs' - copr-fe
-runuser -c '/usr/share/copr/coprs_frontend/manage.py clean_expired_projects' - copr-fe
-runuser -c '/usr/share/copr/coprs_frontend/manage.py clean_old_builds' - copr-fe
+runuser -c '/usr/share/copr/coprs_frontend/manage.py vacuum-graphs' - copr-fe
+runuser -c '/usr/share/copr/coprs_frontend/manage.py clean-expired-projects' - copr-fe
+runuser -c '/usr/share/copr/coprs_frontend/manage.py clean-old-builds' - copr-fe

frontend/conf/cron.daily/copr-frontend-optional

@@ -2,6 +2,6 @@
 
 # Optional Copr frontend tasks to be executed daily.
 
-#runuser -c 'copr-frontend notify_outdated_chroots' - copr-fe
-#runuser -c 'copr-frontend delete_outdated_chroots' - copr-fe
+#runuser -c 'copr-frontend notify-outdated-chroots' - copr-fe
+#runuser -c 'copr-frontend delete-outdated-chroots' - copr-fe
 #/usr/libexec/copr_dump_db.sh /var/lib/copr/data/db_dumps/

frontend/conf/cron.hourly/copr-frontend

@@ -4,5 +4,5 @@
 # hourly.  Don't edit this file manually, it is automatically updated with
 # copr-frontend.rpm.
 
-runuser -c '/usr/share/copr/coprs_frontend/manage.py update_indexes_quick 120 &> /dev/null' - copr-fe
-runuser -c '/usr/share/copr/coprs_frontend/manage.py update_graphs &> /dev/null' - copr-fe
+runuser -c '/usr/share/copr/coprs_frontend/manage.py update-indexes-quick 120 &> /dev/null' - copr-fe
+runuser -c '/usr/share/copr/coprs_frontend/manage.py update-graphs &> /dev/null' - copr-fe

frontend/coprs_frontend/commands/branch_fedora.py

@@ -16,7 +16,7 @@
 )
 def branch_fedora(fedora_version, branch=None):
     """
-    Branch fedora-rawhide-* chroots to fedora-N* and execute rawhide_to_release
+    Branch fedora-rawhide-* chroots to fedora-N* and execute rawhide-to-release
     on them
     """
     rawhide_chroots = coprs_logic.MockChrootsLogic.get_from_name(

frontend/coprs_frontend/commands/create_chroot.py

@@ -50,7 +50,7 @@ def create_chroot_function(chroot_names, branch=None, activated=True):
 )
 @click.option(
     "--activated/--deactivated",
-    help="Activate the chroot later, manually by `alter_chroot`",
+    help="Activate the chroot later, manually by `alter-chroot`",
     default=True
 )
 def create_chroot(chroot_names, branch=None, activated=True):

frontend/coprs_frontend/commands/create_sqlite_file.py

@@ -5,7 +5,7 @@
 
 """
 Create the sqlite DB file (not the tables).
-Used for alembic, "create_db" does this automatically.
+Used for alembic, "create-db" does this automatically.
 """
 
 def create_sqlite_file_function():

frontend/coprs_frontend/commands/rawhide_to_release.py

@@ -22,7 +22,7 @@ def rawhide_to_release(rawhide_chroot, dest_chroot):
     mock_chroot = coprs_logic.MockChrootsLogic.get_from_name(dest_chroot).first()
     if not mock_chroot:
         print("Given chroot does not exist. Please run:")
-        print("    sudo python3 manage.py create_chroot {}".format(dest_chroot))
+        print("    sudo python3 manage.py create-chroot {}".format(dest_chroot))
         return
 
     mock_rawhide_chroot = coprs_logic.MockChrootsLogic.get_from_name(rawhide_chroot).first()

frontend/coprs_frontend/coprs/views/coprs_ns/coprs_general.py

@@ -905,7 +905,7 @@ def copr_forks(copr):
 
 @coprs_ns.route("/update_search_index/", methods=["POST"])
 def copr_update_search_index():
-    subprocess.call(['/usr/share/copr/coprs_frontend/manage.py', 'update_indexes_quick', '1'])
+    subprocess.call(['/usr/share/copr/coprs_frontend/manage.py', 'update-indexes-quick', '1'])
     return "OK"
 
 

frontend/coprs_frontend/run/copr-gdpr-sar.sh

@@ -4,4 +4,4 @@
 # Read more: http://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/gdpr_sar.html
 # Playbook: https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/playbooks/manual/gdpr/sar.yml
 # Usage: SAR_USERNAME=someusername copr-gdpr-sar.sh
-copr-frontend dump_user $SAR_USERNAME
+copr-frontend dump-user $SAR_USERNAME