Open christian-kreuzberger-dtx opened 2 years ago
In general I am in favor of it but I wonder What would be the deprecation procedure
When do you expect the deprecation to happen?
Currently planned for beginning of March.
What is the scope of the deprecation beyond the service itself: documentation, tutorials, blogs/videos that need amendment, etc?
That is up to the original authors of these tutorials, blogs, videos, etc... We're communicating the deprecation, so everyone can adapt in time.
Will there be a grace period for users during which they can migrate and during which they would receive security fixes?
This repo is not actively maintained, is not receiving security fixes, etc..., last release was in summer 2021 with Keptn 0.8.x - So I'm not sure how to answer this question...
Do we plan to remove artifacts after the end of the grace period?
Artifacts will stay where they are, though I'm not sure which artifacts are still available and where they are hosted. I assume it is those artifacts: https://github.com/keptn-sandbox/generic-executor-service#compatibility-matrix
Yes, We are actively using Generic executor service now.
From Keptn Slack:
Hi everyone,
we are going to deprecate and archive this service within the next couple of days.
You can still use generic-executor-service as it is right now. But we would like to urge you to take a look at Job-Executor-Service. We are providing an initial document for migrating in this PR: https://github.com/keptn-contrib/job-executor-service/pull/199/files
This issue serves as an announcement that we will be deprecating this service soon - details below
We plan to deprecate and archive generic-executor-service in favour of job-executor-service - if you're interested in learning more about job-executor, please have a look at https://medium.com/dynatrace-engineering/a-tool-to-execute-them-all-the-job-executor-service-ae0e33bedb3b .
The reason behind this deprecation is very simple: We want to ensure the best quality of experience for our end-users, and drive new users towards the well maintained and tested job-executor-service.
To start with, we will provide a simple migration guide. In the future we plan to provide a more detailed migration guide covering multiple use-cases of generic-executor-service.
Please let us know if you have any questions or concerns below, thanks!
FAQ
What does it look like when it's deprecated?
The repo will be archived on GitHub and we will add a note on top of the README - see https://github.com/keptn-contrib/dynatrace-sli-service for example
When is this going to happen?
Unless any major blockers come up, it will be done roughly at first half of March 2022.
Will I still be able to use the service / download artifacts / install it?
Yes, we are not removing any of these. However, we are not actively maintaining those artifacts, there are no security updates, bug fixes, etc... to it. We strongly advise to migrate to job-executor-service.
I am currently using generic-executor-service, can you help me migrate to job-executor-service?
We will be creating a migration guide in the future. For now, there is no immediate need to switch to job-executor-service. Nevertheless, we strongly advise to take a look at the documents linked above and try out job-executor-service. Also, please let us know via a comment that you are interested in a migration guide, and which kind of setup you are using (this will help us to identify the level of detail of migration guides).