[JBoss JIRA] (TEIID-5508) Add community docs around openshift usage
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5508?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-5508:
----------------------------------
Fix Version/s: 12.1
(was: 12.0)
Priority: Minor (was: Major)
Affects: Documentation (Ref Guide, User Guide, etc.)
Pulling out of 12.0 as it's a low priority to articulate our non-product, non-syndesis openshift positioning.
> Add community docs around openshift usage
> -----------------------------------------
>
> Key: TEIID-5508
> URL: https://issues.jboss.org/browse/TEIID-5508
> Project: Teiid
> Issue Type: Quality Risk
> Components: Documentation
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 12.1
>
>
> We should expand upon docker dealing with running Teiid in a container to reference more about running in openshift - in particular how that affects cluster, load balancing, what health checks can be used, etc.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (TEIID-5555) Create OpenAPI (swagger) metadata document based on OData
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIID-5555?page=com.atlassian.jira.plugin... ]
Ramesh Reddy edited comment on TEIID-5555 at 12/6/18 12:11 PM:
---------------------------------------------------------------
Yes, it is put out by one of the TC guys. It may have an earlier version that supports 2.0 (does not look like he did tag before cutting over to 3.0). The reason to go after 2.0 is the current support of swagger in 3scale is 2.0, which is supposed to move to 3.0 in the next couple of quarters I believe.
was (Author: rareddy):
Yes, it is put out by one of the TC guys. It may have an earlier version that supports 2.0. The reason to go after 2.0 is the current support of swagger in 3scale is 2.0, which is supposed to move to 3.0 in the next couple of quarters I believe.
> Create OpenAPI (swagger) metadata document based on OData
> ---------------------------------------------------------
>
> Key: TEIID-5555
> URL: https://issues.jboss.org/browse/TEIID-5555
> Project: Teiid
> Issue Type: Enhancement
> Components: OData
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Priority: Blocker
> Fix For: 12.1, 11.2.2
>
>
> Automatically generate Swagger metadata document based on OData metadata such the tools like 3Scale can understand the metadata through existing plugins until OData specific plugin is generated. Only swagger 2.0 document is considered for now. 3.0 support is not considered.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (TEIID-5555) Create OpenAPI (swagger) metadata document based on OData
by Ramesh Reddy (Jira)
[ https://issues.jboss.org/browse/TEIID-5555?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-5555:
-------------------------------------
Yes, it is put out by one of the TC guys. It may have an earlier version that supports 2.0. The reason to go after 2.0 is the current support of swagger in 3scale is 2.0, which is supposed to move to 3.0 in the next couple of quarters I believe.
> Create OpenAPI (swagger) metadata document based on OData
> ---------------------------------------------------------
>
> Key: TEIID-5555
> URL: https://issues.jboss.org/browse/TEIID-5555
> Project: Teiid
> Issue Type: Enhancement
> Components: OData
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Priority: Blocker
> Fix For: 12.1, 11.2.2
>
>
> Automatically generate Swagger metadata document based on OData metadata such the tools like 3Scale can understand the metadata through existing plugins until OData specific plugin is generated. Only swagger 2.0 document is considered for now. 3.0 support is not considered.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (TEIID-5555) Create OpenAPI (swagger) metadata document based on OData
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5555?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5555:
---------------------------------------
https://github.com/oasis-tcs/odata-openapi looks to be the most promising starting point. It's for openapi 3 - is there a reason you want 2.0 support?
This work seems to account for most of my concerns. It generates explicit paths to two entity levels and shows all possible odata url parameters for each path. It also shows the full result entity, such that usage of expand would be accounted for. $expand though seems limited - as the openapi does not seem to describe using query options in parens in the expand e.g. {code}$expand=*($levels=1){code}
So it's very verbose, but does a reasonable job of representing the api.
> Create OpenAPI (swagger) metadata document based on OData
> ---------------------------------------------------------
>
> Key: TEIID-5555
> URL: https://issues.jboss.org/browse/TEIID-5555
> Project: Teiid
> Issue Type: Enhancement
> Components: OData
> Reporter: Ramesh Reddy
> Assignee: Ramesh Reddy
> Priority: Blocker
> Fix For: 12.1, 11.2.2
>
>
> Automatically generate Swagger metadata document based on OData metadata such the tools like 3Scale can understand the metadata through existing plugins until OData specific plugin is generated. Only swagger 2.0 document is considered for now. 3.0 support is not considered.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months