-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop rest-client template ? #113
Comments
As the goal of the
but without the skeleton of an application AND using only the quarkus starters |
I think that it is time to think about how we design a new Quarkus Application template. Should we copy/paste an existing one and change the code with the risk that we will duplicate many common resources: Tekton, ArgoCD, Helm, etc, increase the maintenance cost when changes should be propagated to x template folders, etc or instead Should we try to create a generic Quarkus Application template able to deal with different examples such as ChatBot, TODO, REST server/client, etc and where the examples are handled under their specific skeleton folder but selected using an enum. Here is an example where the CI skeletons are selected using enum, etc - |
It depends on if we have deadlines that might favor a quicker solution or how often we will need to do changes on the template but in general I think the second solution is the better long-term solution despite its initial complexity. This approach makes maintenance easier because centralizes common functionality and can reduce duplication than copy/pasting and dealing with existing code. |
I think that now that we have a more concrete yet generic enough example (the chatbot) that shows how to consume an api, maybe we should drop the rest-client template.
The text was updated successfully, but these errors were encountered: