COPR modular odds

[Cristian Balint]

Dear COPR Team,

Would like to ask a few questions after hitting odds trying to use the
modular features.
My interest is the ability to have mixed stable/nightly releases (user
switchable), so the modularity feature would be ideal.

After looking at several related online resources including copr-framework
source code I decided to ask right here:

#1. Using specific modulemd.yaml, the new module +creates , +builds, +tags
all components picked via repo/ref git path.

   $ copr build-module test --yaml dummy.yaml

   - But running once again (trying to add updated package) with updated
ref/tags leads to errors:

   $ copr build-module test --yaml dummy.yaml
   "Module dummy-master-20220701234448 already exists"

   Q: Then how can add *newer* package builds to an existing module ?

   Q: Modular builds in the web-frontend expose +extra "Module:" tag, how
can copr-cli launch builds into such a module-tag ?

#2.  Let's assume at #1 modules are created *once* as fixed object and it
is not possible to add/alter with newer package builds:

  Q: How can one delete an existing module from COPR (assume it was created
erroneously or obsoleted) ?

  Q: How can I avoid having (too) many separate *.repo for each separate
module within a single project ?

  Q: Is there a unified way to add only once a *.repo (easy to advertise
URL) and see all the modules within that project ?


Thank you,
~Cristian.