Keep track of operations per formation assignment

[nyordanoff]

Description

Currently, we are not storing any information about the current (or past) operations happening on an assignment. We use the state to calculate what was the last operation that happened whenever we need that information: this results in states like: CREATE_ERROR, CREATE_READY, DELETE_ERROR, DELETE_READY, etc...

This PR introduces the new assignment_operation entity and manages its lifecycle. The operation can be either ASSIGN or UNASSIGN.

Changes proposed in this pull request:

• introduce assignment_operation entity along with dataloaders, service and repo layer
• the assignment_operation entity has some fields entirely for troubleshooting purposes for the future - triggered_by, started/finished_at_timestamps
• create assignment_operation for all existing FAs based on their state
• manage operation lifecycle (create/update/delete) - on assign/unassign/resync/reset/status report
• rewrite some notification e2e tests in the new test format

Pull Request status

• Implementation
• Unit tests
• Integration tests
• chart/compass/values.yaml is updated
• Mocks are regenerated, using the automated script

[ognyvrac]

/unhold

[ognyvrac]

/hold

[kyma-bot]

@nyordanoff: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pre-main-compass-gke-benchmark	b20ac95	link	false	/test pre-main-compass-gke-benchmark

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[kyma-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dzahariev, StanislavStefanov

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [StanislavStefanov,dzahariev]
• components/director/cmd/ns-adapter/OWNERS [dzahariev]
• components/director/cmd/ordaggregator/OWNERS [dzahariev]
• components/director/cmd/systemfetcher/OWNERS [dzahariev]
• components/director/internal/domain/formation/OWNERS [StanislavStefanov]
• components/director/internal/domain/formationassignment/OWNERS [StanislavStefanov]
• components/director/internal/formationmapping/OWNERS [StanislavStefanov]
• components/director/internal/tenantfetchersvc/OWNERS [dzahariev]
• tests/director/tests/notifications/OWNERS [StanislavStefanov]
• tests/instance-creator/OWNERS [StanislavStefanov]
• tests/pkg/notifications/OWNERS [StanislavStefanov]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[nyordanoff]

/hold cancel