First commit of sample configuration, Haufe-Lexware/wicked.haufe.io#64

static/apis/apis.json

@@ -0,0 +1,43 @@
+{
+  "apis": [
+    {
+      "id": "petstore",
+      "name": "Petstore",
+      "desc": "This is a sample Petstore server. You can find out more about Swagger at [http://swagger.io](http://swagger.io).",
+      "auth": "key-auth",
+      "tags": [
+        "Sample"
+      ],
+      "plans": [
+        "basic",
+        "unlimited"
+      ]
+    },
+    {
+      "id": "petstore-oauth",
+      "name": "Petstore OAuth",
+      "desc": "This is a sample Petstore server secured via OAuth 2.0 Client Credentials flow.",
+      "auth": "oauth2",
+      "tags": [
+        "Sample"
+      ],
+      "requiredGroup": "dev",
+      "plans": [
+        "basic",
+        "unlimited"
+      ],
+      "settings": {
+        "token_expiration": 3600,
+        "enable_client_credentials": true
+      }
+    }
+  ],
+  "_links": {
+    "self": {
+      "href": "/apis"
+    },
+    "plans": {
+      "href": "/plans"
+    }
+  }
+}

static/apis/desc.md

@@ -0,0 +1,3 @@
+Click on an API in order to see more information on it and to subscribe to it. Only after subscribing, you will get an API key which enables you to actually call the API.
+
+Here you can add custom text and generic information on your APIs, and it will appear on the `/apis` page. As the selection of APIs may depend on the groups a user belongs to, you should perhaps not assume you can refer to specific APIs, as long as they are not publicly visible.

static/apis/petstore-oauth/config.json

@@ -0,0 +1,10 @@
+{
+    "api": {
+        "upstream_url": "http://petstore.swagger.io/v2",
+        "request_path": "/petstore-oauth",
+        "preserve_host": false,
+        "strip_request_path": true,
+        "name": "petstore-oauth"
+    },
+    "plugins": []
+}

static/apis/petstore-oauth/desc.md

@@ -0,0 +1,3 @@
+This is the sample Swagger file from [swagger.io](http://swagger.io). This is picked as a sample as the backend service is always available at no charge, which makes it easier to wire it in your own API gateway.
+
+The reason why this API is present twice is that the first API is using API key authorization, and this one uses OAuth 2.0 client credential flow authorization.