Update scc proxy engine to support LTSS

jesusbv commented 3 months ago

Description

Update scc_proxy engine to support LTSS scenario

How to test

On a registered PAYG instance, adding LTSS extension with a valid registration code must succeed

Change Type

Please select the correct option.

[ ] Bug Fix (a non-breaking change which fixes an issue)
[X] New Feature (a non-breaking change which adds new functionality)
[ ] Documentation Update (a change which only updates documentation)

Checklist

Please check off each item if the requirement is met.

[X] I have reviewed my own code and believe that it's ready for an external review.
[X] I have provided comments for any hard-to-understand code.
[ ] I have documented the MANUAL.md file with any changes to the user experience.
[ ] If my changes are non-trivial, I have added a changelog entry to notify users at package/obs/rmt-server.changes.

Review

Please check out our review guidelines and get in touch with the author to get a shared understanding of the change.

bear454 commented 3 months ago

Before this gets merged, someone from the SCC team needs to approve the stubbed SCC requests & responses.

jesusbv commented 3 months ago

Any further comments I have are purely stylistic.

so, all the changes left are more cosmetic than adding/removing functionality, am I wrong ? if I understood it right, then we can merge this PR so we can move on to the next PR and have a subsequent PR (once all the LTSS functionality is merged) to refactor auth on scc_proxy engine Thoughts ?

SUSE / rmt