[POLL] Remove pre and post task functionality #2284
Replies: 2 comments 2 replies
-
You arguments are valid, but I'd like challenge the following:
Let's say that in the next deployment, we need to perform a DB migration. If the DB migration KeptnTask fails, it makes sense to prevent the deployment from progressing since the DB is not ready to support the new version of my App. Post tasks are essential at the moment to allow users to have a "promotion" step so the new App version can be propagated to the next environment |
Beta Was this translation helpful? Give feedback.
-
I think this discussion can be closed. |
Beta Was this translation helpful? Give feedback.
-
Note: This poll specifically and only discusses the task functionality NOT the SLO evaluation functionality.
Keptn (currently) offers the following core functionality:
I understand the applicability of 2, 3 and 4, but I don't see the applicability of 1.
If the pre and post checks were truly fully functional, Keptn would allow workflow-like abilities. But it has been stated by the maintainers that this explicitly is out of scope for the project.
By removing this functionality, we:
a) Simplify the development and maintenance effort
b) Remove the danger of Keptn by removing it's ability to block a deployment (without a good reason ie. a failing SLO)
c) Simplify the messaging of what Keptn is and who it is aimed at
6 votes ·
Beta Was this translation helpful? Give feedback.
All reactions