Add json_creation_script for local usage

[ktsamis]

What does this PR change?

Add json_creation_script for local usage. Note that this is not integrated for any pipelines yet, only for running locally in your workstation.

GUI diff

No difference.

• [x] DONE

Documentation

• No documentation needed: only internal and user invisible changes

• [x] DONE

Test coverage

• No tests: This is a script for ease of use for QE, meant to be run locally

• [x] DONE

Links

Fixes https://github.com/SUSE/spacewalk/issues/18343 Tracks no other PR is needed.

• [x] DONE

Changelogs

Make sure the changelogs entries you are adding are compliant with https://github.com/uyuni-project/uyuni/wiki/Contributing#changelogs and https://github.com/uyuni-project/uyuni/wiki/Contributing#uyuni-projectuyuni-repository

If you don't need a changelog check, please mark this checkbox:

• [x] No changelog needed

If you uncheck the checkbox after the PR is created, you will need to re-run changelog_test (see below)

Re-run a test

If you need to re-run a test, please mark the related checkbox, it will be unchecked automatically once it has re-run:

• [ ] Re-run test "changelog_test"
• [ ] Re-run test "backend_unittests_pgsql"
• [ ] Re-run test "java_pgsql_tests"
• [ ] Re-run test "schema_migration_test_pgsql"
• [ ] Re-run test "susemanager_unittests"
• [ ] Re-run test "javascript_lint"
• [ ] Re-run test "spacecmd_unittests"

[nodeg]

I found some issues while using the tool and doing the steps manually with @Bischoff. See https://gitlab.suse.de/ktsamis/json_creation_script/-/issues/1

[srbarrios]

We need to ask Jenkins maintainers about SSH key to authenticate via API to build.suse.de

[ktsamis]

I found some issues while using the tool and doing the steps manually with @Bischoff. See https://gitlab.suse.de/ktsamis/json_creation_script/-/issues/1

That has been fixed, sle15sp4 was added and SSH minions don't require custom repos since they don't install any packages but are only handled via ssh.

[ktsamis]

I will do tomorrow a small change adding EL9 and renaming centos8 to rocky8, and then merge

[ktsamis]

I think this is ready to be merged.

[nodeg]

I do not see anything SLE Micro related in the list. Is this simply handled as a normale SLES 15 SPx?

[juliogonzalez]

I do not see anything SLE Micro related in the list. Is this simply handled as a normale SLES 15 SPx?

I did not review the PR, but aware: SLE Micro uses different channels, so it should generate separate repos for the client tools MI and the salt/salt bundle MIs

[ktsamis]

I added the missing products. Only one question do we need slemicro 5.1 ? I only added 5.2 @juliogonzalez

[juliogonzalez]

I added the missing products. Only one question do we need slemicro 5.1 ? I only added 5.2 @juliogonzalez

@admd what was decided as supported? And by supported I mean: customers can create bug reports and they can even become L3s.

[admd]

I added the missing products. Only one question do we need slemicro 5.1 ? I only added 5.2 @juliogonzalez

@admd what was decided as supported? And by supported I mean: customers can create bug reports and they can even become L3s.

SLE Micro support is still tech preview but we plan to remove tech-preview label with 4.3.4. SLE Micro 5.1 is out of scope anyways.

[mcalmer]

... but 5.3 is in scope. Don't forget it

[juliogonzalez]

I added the missing products. Only one question do we need slemicro 5.1 ? I only added 5.2 @juliogonzalez

@admd what was decided as supported? And by supported I mean: customers can create bug reports and they can even become L3s.

SLE Micro support is still tech preview but we plan to remove tech-preview label with 4.3.4. SLE Micro 5.1 is out of scope anyways.

For the record, the doc does not mention specific SLE Micro versions, in the same way it doesn't mention SPs for SLE15.

Not sure if you really want this only at the releases notes for 4.3.4, or if you want doc to add at least a WARNING somewhere at the doc.