Create/update systems and license keys

[MatthiasWinzeler]

This PR adds the functionality discussed in issue #15.

Scope

• The PR adds two modules:
  • license_keys, which allows creating and updating systems and their license keys.
    It is closely modeled after the interactions in the portal https://me.sap.com/licensekey, meaning that systems and license keys are always updated together (i.e. you cannot just create new license keys, but you have to edit the system, add license keys, and submit everything together).
  • systems_info, which allows retrieving existing systems (i.e. its system number), so that the system update/license key creation can be done in an idempotent manner (see example below).
• What is intentionally out of scope:
  • The entity 'Installation' - the parent entity of systems - has to be created manually beforehand (and its installation number passed on to the module). We think that it's not worth to offer automation for creating installations, as installations are usually created once per customer and only the systems and license keys change frequently.
  • The module doesn't allow deletion of systems or license keys. We found that decommissioning of SAP systems is usually a manual process anyway. But if desired, we can add deletion to this module/PR.

Example

An example usage of the module which allows to idempotently create or update a system and retrieve the license key file:

- name: test license key creation
  hosts: localhost
  tasks:

  - name: get existing system
    community.sap_launchpad.systems_info:
      suser_id: S1234
      suser_password: password
      filter: "Insnr eq '123456789' and sysid eq 'B01' and ProductDescr eq 'SAP S/4HANA'"
    register: result

  - name: create license keys
    community.sap_launchpad.license_keys:
      suser_id: S1234
      suser_password: password
      installation_nr: 123456789
      system:
        nr: "{{ result.systems[0].Sysnr | default(omit) }}"
        product: SAP S/4HANA
        version: SAP S/4HANA 2022
        data:
          sysid: B01
          sysname: Test-System
          systype: Development system
          sysdb: SAP HANA database
          sysos: Linux
          sys_depl: Public - Microsoft Azure
      licenses:
        - type: Standard - Web Application Server ABAP or ABAP+JAVA
          data:
            hwkey: H1234567890
            expdate: 99991231
        - type: Maintenance Entitlement
          data:
            hwkey: H1234567890
            expdate: 99991231
    register: result

  - name: Display the license file containing the licenses
    debug:
      msg:
        - "{{ result.license_file }}"

I tested the following use cases to ensure full idempotency.

• If no system exists, a new system and its licenses are created
• If a system exists and passed with system.nr, its data attributes are updated and any changed licenses applied. If the licenses had no changes, they are not updated.

Let me know if you need more examples (should we create a sample playbook in the repo?), more extensive documentation or other changes. Please also let me know if I have to sign any CLA. Eager to get your feedback!

[rainerleber]

Hi @MatthiasWinzeler thank you for contributing. I will review this PR soon.

[rainerleber]

First Review is Done. @MatthiasWinzeler thank you for this PR we appreciate it.

[MatthiasWinzeler]

@rainerleber many thanks for your feedback! I took care of the obvious comments and added follow-up questions where it was unclear to me how we proceed.

[rainerleber]

@MatthiasWinzeler thanks for clarify the questions. Only a few things are left :-) after that we are ready to merge I think.

[MatthiasWinzeler]

@rainerleber thanks - merged your suggestions and responded your other comments. Can you give it a final review?

[MatthiasWinzeler]

@rainerleber FYI, cleanup PR is in #17

[rainerleber]

LGTM, @MatthiasWinzeler thank you for the great work