[
https://issues.redhat.com/browse/TEIIDSB-197?page=com.atlassian.jira.plug...
]
Steven Hawkins commented on TEIIDSB-197:
----------------------------------------
I believe you are too focused on the process improvement over the
functionality, I am weighted more on functionality right now.
From my perspective there's no harm in making our lives as easy as
possible down the road.
I saw deficiencies last time around
Yes, once pushed.
Right now I am viewing this as crud work that is not bringing much
functionality thus reluctance to go jump all over it
You'll need to accept that considerations of design and technical debt must occur
along side feature work. How it all gets captured and prioritized has a lot of
flexibility.
Right now I am viewing this as crud work that is not bringing much
functionality thus reluctance to go jump all over it
Capturing an issue like this does not mean that it needs to be worked by you or in the
near term. Since there are no design docs and little docs in general about the workings
of the operator in regards to dependency handling at the very least issues like these help
others understand what is there.
Add a module for each external source
-------------------------------------
Key: TEIIDSB-197
URL:
https://issues.redhat.com/browse/TEIIDSB-197
Project: Teiid Spring Boot
Issue Type: Enhancement
Reporter: Steven Hawkins
Assignee: Ramesh Reddy
Priority: Major
To simplify the logic in the operator each external source should be represented by a
maven artifact - org.teiid:spring-data-x. Any dependency management would be handled in
that module and not in the operator - to remove the need for a config file containing
driver versions. Additionally property handling should be moved into Teiid Spring Boot
such that the operator does not need to know what property prefix is expected.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)