Add support for additional module registration

[BillAnastasiadis]

This adds a task to add any number of additional modules that require a regcode during execution of registration.yaml playbook. The module names and regcodes are injected in the command that calls the playbook as arguments, either if the playbook is ran standalone, or if it is run through the config.yaml file.

The format should be like this:

create:
    - registration.yaml (.......other variables here......) -e sles_modules='[{"key":"<module_to_activate","value":"<regcode-for-module>"}]'

or without the create part if running playbook directly.

I tried 2 manual deployments, one with use_suseconnect=true and one without it, and ran ansible (containing only registration module).
I put this in config.yaml, in the line calling the registration.yaml file :

create:
    - registration.yaml -e reg_code=...-e email_address='' -e sles_modules='[{"key":"(...LTSS module name)","value":"(ltss regcode)"}]'

• first case, general registration done with SUSEConnect, then new task also ran with suseconnect, after the playbook LTSS is activated.
• second case, general registration done with registercloudguest, new task ran with SUSEConnect, after the playbook LTSS is activated.

Used: https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_loops.html#iterating-over-a-list-of-hashes (added a label as proposed in https://docs.ansible.com/ansible/latest/playbook_guide/playbooks_loops.html#limiting-loop-output-with-label, not sure if we need it in our case)

• Related ticket: https://jira.suse.com/browse/TEAM-9808

[mpagot]

Please document the new variable in https://github.com/SUSE/qe-sap-deployment/tree/main/docs/playbooks

[lpalovsky]

LGTM

[mpagot]

leave out

- ansible_facts['distribution_major_version'] == "12"

the task is generic for any kind of SCC channels. Our handling of LTSS is specific for 12sp5 but Ansible Task code is totally agnostic
about it

[mpagot]

Suggested change

	There's a task to add any number of additional modules that require a regcode during execution of registration.yaml playbook. The module names and regcodes are injected in the command that calls the playbook an argument with the form of a list of hashes (named sles_modules), either if the playbook is ran standalone, or if it is run through the config.yaml file.
	There's a task allowing register additional modules that require a dedicated regcode.
	The module names and regcodes can be provided in the `ansible-playbook` command line as list of hashes (named sles_modules).

[mpagot]

can you change example using 2 modules? Is it

-e sles_modules='[{"key":"<module_to_activate_1>","value":"<regcode_for_module_1>"}, {"key":"<module_to_activate_2>","value":"<regcode_for_module_2>"}]'

[mpagot]

LGTM

[mpagot]

Also this one deserve an explanation:

• The article suggest to update cloud-regionsrv-client for 12sp5 PAYG
• zypper up only works if image is registered

[alvarocarvajald]

LGTM. Just a question/suggestion/comment.

[alvarocarvajald]

I think this line can be removed. Even though we're working on enabling LTSS/LTSS-ES in 12-SP5, updating this package should work in all supported Service Packs.

[mpagot]

LGTM