EVEREST-458 Restart everest operator once a new version of operator i…

[gen1us2k]

…s installed

CHANGE DESCRIPTION

Problem:
EVEREST-458

Short explanation of the problem.

During the installation of a database engine operator, CLI does not ensure the deployment has been rolled out. Hence for MongoDB installation, since it's too long and the rollout is slower than others the everest operator gets restarted and after the restart, a psmdb operator is completely deployed.

Also, during the QA process and after a discussion we decided to restart the everest operator only if a new version of an operator was deployed

Solution:

Wait for the deployment rollout during the installation of an operator and restart the everest operator once it a new version of a database engine operator is deployed.

CHECKLIST

Jira

• Is the Jira ticket created and referenced properly?

Tests

• Is an Integration test/test case added for the new feature/change?
• Are unit tests added where appropriate?

[oksana-grishchenko]

So the "new version of a database engine operator" means a new type of operator and it has nothing to do with the versioning of an operator itself. Was a bit confused at first by the description.
Looks good, should work 👍

[recharte]

The DoRolloutWait was an important piece, well done 💪