feat: allow to update activations via the patch API

[bzwei]

Activations must be in disabled mode. Most fields are editable.

AAP-37295: Edit an existing activation

[bzwei]

e2e test failure is fixed by https://github.com/ansible/eda-qa/pull/447

[mkanoor]

@bzwei Since we might be updating and restarting an Activation should we log a line here to indicate that the Activation has been updated, since if the user picks up different rulebook during an update the old Rule Audit wont make any sense. Having a log line that indicates that the Activaiton has been updated since creation will give some context to the old Rule Audits. The old Rule Audits point to an Activation Instance log and this message will tell us that the user has updated this Activation.

eda-server/src/aap_eda/services/activation/activation_manager.py

Line 200 in 69b06ef

LOGGER.info(

[sonarqubecloud]

Quality Gate failed

Failed conditions
11.8% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud

[bzwei]

@bzwei Since we might be updating and restarting an Activation should we log a line here to indicate that the Activation has been updated, since if the user picks up different rulebook during an update the old Rule Audit wont make any sense. Having a log line that indicates that the Activaiton has been updated since creation will give some context to the old Rule Audits. The old Rule Audits point to an Activation Instance log and this message will tell us that the user has updated this Activation.

eda-server/src/aap_eda/services/activation/activation_manager.py

Line 200 in 69b06ef

LOGGER.info(

@mkanoor Here I have the log https://github.com/ansible/eda-server/pull/1174/files#diff-3aa1d8dc47ee0af34b544249cc19758b5919dbddf7057e84dc032f49f6235f33R176. Is it sufficient?

[mkanoor]

@bzwei That is an audit log that doesn't come out to the activation_instance log. That audit log was added by @zkayyali812 for audit trail. We need a one liner in the rulebook process log that is visible in the UI that shows it is an updated Activation. When you look at the the "Rule Audit" in out UI and click on the Activation it opens up our Rulebook process log thats where we would like to see it has been updated.

[bzwei]

@bzwei That is an audit log that doesn't come out to the activation_instance log. That audit log was added by @zkayyali812 for audit trail. We need a one liner in the rulebook process log that is visible in the UI that shows it is an updated Activation. When you look at the the "Rule Audit" in out UI and click on the Activation it opens up our Rulebook process log thats where we would like to see it has been updated.

We do not know whether the activation has been updated unless we introduce a new field to its model. This new line in the rulebook process log will be printed in every restart.