account check made explicit - cleanup

[DaanHoogland]

Description

This PR cleans up and restructures the code that checks and applies invites on update.

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (improves an existing feature and functionality)
• Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

• Major
• Minor

Bug Severity

• BLOCKER
• Critical
• Major
• Minor
• Trivial

Screenshots (if appropriate):

How Has This Been Tested?

should be tested by the project smoke tests.

[DaanHoogland]

@blueorangutan package

[blueorangutan]

@DaanHoogland a Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

[blueorangutan]

Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 2887

[nvazquez]

@blueorangutan test

[blueorangutan]

@nvazquez a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

[blueorangutan]

Trillian test result (tid-3617)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 31379 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr6122-t3617-kvm-centos7.zip
Smoke tests completed. 92 look OK, 0 have errors
Only failed tests results shown below:

Test	Result	Time (s)	Test File

[nvazquez]

Code LGTM

[rohityadavcloud]

LGTM, can you add unit test (optionally also a marvin test case if it doesn't already exist) for this change?

[DaanHoogland]

LGTM, can you add unit test (optionally also a marvin test case if it doesn't already exist) for this change?

As stated in the description @rohityadavcloud "should be tested by the project smoke tests."

[Pearl1594]

code LGTM