[
https://issues.jboss.org/browse/TEIID-5131?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5131:
---------------------------------------
I have emulated the infinispan approach to create an openshift image for our
standalone-teiid.xml - infinispan adds a clustered.xml and cloud.xml to the wildfly
standalone configurations and they also inject a configuration via the template.
The default security realm is used to add application and management users. This is fine
for a first cut, but we'll need to have an option to support keycloak/openshift sso
(especially for admin).
I should have this wired for just salesforce for jdbc access on Monday, such that the
template will accept the sf credentials and handle the appropriate vdb / resource adapter
configuration. I want to make sure I have a handle on exposing JDBC as a route and to
validate clustering/ha with this template (although other than ha there won't be much
benefit).
The next step will be to expose odata for an existing provisioned instance. I'm not
sure if that can be done via templates or if ansible will be required.
Create ansible playbooks for the ansible service broker
-------------------------------------------------------
Key: TEIID-5131
URL:
https://issues.jboss.org/browse/TEIID-5131
Project: Teiid
Issue Type: Enhancement
Components: Build/Kits
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.1
For some of the most common usage patterns, we should create playbooks that contribute
service brokers via the ansible service broker. This could be:
salesforce as db
couchbase as db/odata
mongodb as db/odata
other openshift databases as odata
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)