[Feature Request] Ability to add Release versions to existing repositories

[KayTeeFive]

Hi,

It would be useful to have the ability to add new Release versions to repositories after they have already been created.

For example,
I created test-repo with release version 4.18.

Later, I may need to add support for 4.19 without recreating the repository from scratch.

This feature would simplify repository management and make it easier to maintain repositories across multiple release versions.

Thanks.

[CrAazZyMaN21]

Hi, this already works when you create a new repository and just name it the same just with the new release version.

[KayTeeFive]

Hi, this already works when you create a new repository and just name it the same just with the new release version.

Hi,
Interesting workaround, thanks. But there is a problem...

Technically you found a bug: you should not be allowed to create a repo with the same name that already exists.

It's very bad practice to reuse that workaround in prod env, because, creating a new repo should mean that new repo is empty after creation.

[CrAazZyMaN21]

Hi, not really since the release version differs. When you add a new repo with the same name and same release version an error appears. Maybe lbr38 will improve this with 6.0.0 but no clue. My wild guess is that this is intentional since 5.0.0

[lbr38]

Hello

@CrAazZyMaN21 understood it all.

Each repository is independant and has its own URL so it should not be a problem creating a repository with the same name.

For example, I have sync Alma Appstream repo for releases ver. 8, 9 and 10. They are individually accessible via their respective URLs:

http://repomanager-dev.localhost/repo/rpm/almalinux-appstream/8/preprod
http://repomanager-dev.localhost/repo/rpm/almalinux-appstream/9/preprod
http://repomanager-dev.localhost/repo/rpm/almalinux-appstream/10/preprod

So there should be no conflict and I don't see what the bad practice you mentioned is. May be you could clarify a bit @KayTeeFive?

Thanks

[KayTeeFive]

As for me, it's sound risky when for adding new Release version you need go to Create new repo flow.
Simple validation mistake in the code can lead to big problems. I can be wrong and to be little bit paranoid :-D

[lbr38]

My suggestion is to have a test instance to make all your experiments and clear up your doubts.
Every program can have errors and mistakes, but adding more and more features can also bring new bugs and complexities that can lead to unexpected behavior and problems.