Using the Swagger API is certainly interesting but not enough if by example
I would like to create a yaml or json file (BuildConfig, DeploymentConfig,
A developer could use this doc (
...) to learn for the BuildConfig process the spec, fields to be used, what
are the mandatory/optional fields, their type, values, ...
But we should provide yaml/json reference files, json schemas (see -->
http://json-schema.org/) in order to help them to validate that the config
file used is compliant to the spec, that they are using the correct values
or simply to discover the features supported by example :
Make sense ?
On Mon, Sep 19, 2016 at 7:30 PM, Charles Moulliard <cmoul...@redhat.com>
> The Swagger GUI is available at this address : https://openshift-server:
> On Mon, Sep 19, 2016 at 7:13 PM, Charles Moulliard <cmoul...@redhat.com>
>> Is swagger packaged with OpenShift Origin to list the operations, ... ?
>> On Mon, Sep 19, 2016 at 6:45 PM, Clayton Coleman <ccole...@redhat.com>
>>> That is generally the swagger docs (1.2 currently) listed here:
>>> On Mon, Sep 19, 2016 at 8:37 AM, Charles Moulliard <cmoul...@redhat.com>
>>>> Is it defined somewhere for each OpenShift Artifacts (Template,
>>>> DeploymentConfig, Buildconfig, ...), the version of the "syntax" supported
>>>> according to the OpenShift Server (1.2, 1.3, ...) where it will be executed
>>>> Syntax = Json or YAML Structure supported
>>>> Example: The DeploymentConfig Template is described here https://
>>>> yments.html#dev-guide-deployments for the Api Version = 1
>>>> - Is Api Version 1 the Api supported by OpenShift Origin 1.x ?
>>>> OpenShift enterprise 3.x ?
>>>> - Is it possible to have a Reference Template for each Artifact that we
>>>> can use top of OpenShift ? Maybe from a Github repo ?
>>>> users mailing list
users mailing list