[ https://issues.redhat.com/browse/TEIIDSB-197?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDSB-197: ---------------------------------------- And that is exactly what I'm proposing to address here... I'm not sure why I'm having such a hard time getting through to you on some of this :( That should be completely discounted as a possibility. You can override dependencies in the crd's themselves to do it on an ad hoc basis in your own custom operator would make it extremely difficult to know what versions of things were actual in use. Let me rephase that - you currently believe you can do as good of a job of dependency management as maven in a single file. However I would counter that once you encounter sources that need more than a single dependency and/or you need better traceability - then it would be best to just rely on a standard system. As far as the operator is concerned, yes there is no Teiid Spring Boot specific prefix needed, just a general convention - then let Teiid Spring Boot convert the properties to the actual property. So for example default everything to spring.teiid.data.alias.property and let Teiid Spring Boot determine if it needs to actually be spring.datasource, spring.datasource.xa, etc. I get that as a goal. But keep in mind it's not as straight forward as it seems. There's a lot of pooling related properties that could be included, all of the XADataSource properties (which aren't explicitly named by spring), or other similar more free form / source driven properties. The more you commit to assumptions, the more rigid and brittle things will become (for example are we prepared to fully commit to a particular pooling implementation, or do we need to come up with abstractions). -- This message was sent by Atlassian Jira (v7.13.8#713008)