Comment 3 for bug 2003198

Reviewed: https://review.opendev.org/c/starlingx/cert-manager-armada-app/+/871081
Committed: https://opendev.org/starlingx/cert-manager-armada-app/commit/0a65cd0d90370c11ff7f7cf334c5f42fd9d7d3dd
Submitter: "Zuul (22348)"
Branch: master

commit 0a65cd0d90370c11ff7f7cf334c5f42fd9d7d3dd
Author: Dan Voiculeasa <email address hidden>
Date: Thu Jan 19 11:07:44 2023 +0200

    Add lifecycle hook and configure one semnatic check

    If sysinv-conductor is restarted while cert-manager is running it's
    status will be changed from 'applying' to 'uploaded'[1]. 'applying'
    state can be obtained from an 'applied' state by framework
    automatically re-applying the app. In fact it is desired to keep
    the 'applied' state without manual intervention.

    Purpose of this commit is to allow this app to be auto applied from
    'uploaded' state.

    This is just extending the base lifecycle from conductor, configuring
    the semantic check for auto apply.

    Tests on AIO-SX:
    PASS: bootstrap
          cert-manager is in 'applied' state
    PASS: deploy, obtain unlocked enabled available
          cert-manager is in 'applied' state
    PASS: after unlock force uploaded state and observe app auto-applied
    PASS: system application-remove is rejected
    PASS: system application-remove --force is allowed
    PASS: emulate bootstrap by creating /var/run/.ansible_bootstrap,
          and observe app is not auto-applied from uploaded state

    [1]: https://review.opendev.org/c/starlingx/config/+/870960
    Closes-Bug: 2003198
    Signed-off-by: Dan Voiculeasa <email address hidden>
    Change-Id: I37a9c740f0b7906c9f1fb1a0be9bf0b117a6df03