How to Call the OpenShift REST API From C#
When you want to do automated tasks for builds and deployments with Red Hat OpenShift, you might want to take advantage of the OpenShift REST API. In scripts, you can use oc CLI command, which talks to the REST APIs. However, there are times when it is more convenient to do this directly from your C# code without having to invoke an external program. This is the value of having an infrastructure platform that is exposed as services with an open API.
If you want to call the API from your C# code, you have to create a request object, call the API, and parse the response object. The upstream project, OpenShift Origin, provides a Swagger 2.0 specification, and you can generate a client library for each programming language. Of course, C# is supported. This isn’t a new approach, Kubernetes has a repository that is generated by Swagger Codegen. https://goo.gl/m7LpCt #DataIntegration #ML
Reuse Driven by DataType
#ICYMI: Raml 1.0 introduces a new concept called DataType. This fragment is used to declare type in a separate yaml file. This is not just a simplification of JSON schema to conform raml/yaml. It also brings simple improvements and syntax sugar that allows to write types in more concise form, and therefore more readable. In this article, we will look at how to define our own data types and reuse them in the API and its implementation.
Custom Data Types
Anyone who has designed an API knows that it is probably always necessary to define custom data structures as simple data types are not meaningful enough. Below, you can see data types that are supported by Raml 1.0. We have a group of scalar types like integer, date-only, and so on. We have also compound structures like array and objects. XSD and JSON schema are a separate type as a developer can still share custom types using these schemas. https://goo.gl/4t4ubx #DataIntegration #ML