Deprecate the CustomStateCheck feature #1616
Assignees
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
Comments
janmedrek
added
the
kind/feature
jeremyharisch
changed the title
This was referenced Jul 24, 2024
kyma-bot
pushed a commit
to kyma-project/template-operator
that referenced
this issue
Jul 30, 2024
**Description** Add deprecation note for the `customStateCheck` attribute: **Related issue(s)** kyma-project/lifecycle-manager#1708 kyma-project/lifecycle-manager#1616 --------- Co-authored-by: Małgorzata Świeca <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
With the separation of the statuses that will be introduced in #1471, there is no longer a need to rely on the Module resources to determine the overall status of the Kyma Module.
Instead, we should only take into the account Manifest State of the module, thus this feature is no longer required and should be deprecated.
Reasons
We want a clear separation of statuses without going into module-related resources and logic.
Acceptance Criteria
Feature Testing
No response
Testing approach
No response
Attachments
No response
The text was updated successfully, but these errors were encountered: