Tyk and consul service descovery integration

[Olu]

@Josh

Ok, looks like it is borked for all GW versions above 3.2. So for the moment if this is something in the hot path for your evaluation, the options are either step back gw version for now or I can provide you with a workaround using body transformation to cheat it basically. Let me know and apologies for you running into this.

It seems that there was a body transformation hack.

[Rutul_Shah]

Josh, can you please tell where exactly we need to add this block ? Can you share a sample API doc json where you would keep this block ?

[Rutul_Shah]

Jameso,

Can you share your json for reference please ? I am facing exactly the same issue ? But I am not getting where exactly we need to add this block in my json.

[Olu]

@Rutul_Shah

Josh, can you please tell where exactly we need to add this block ? Can you share a sample API doc json where you would keep this block ?

@Radhika Have you had a look at our documentation. There are two types of body transformations. Request and Response. What you what is the response and that can be seen here Response Body
directly underneath the request doc

[Olu]

@Rutul_Shah

Can you share your json for reference please ? I am facing exactly the same issue ? But I am not getting where exactly we need to add this block in my json.

The JSON reference can be seen here

@Jameso

[
    {
        "ID": "5d5c41c2-b65a-3855-4119-102e0e72a765",
        "Node": "ip-10-0-0-2",
        "Address": "10.0.0.2",
        "Datacenter": "eu-west-1",
        "TaggedAddresses": null,
        "NodeMeta": null,
        "ServiceKind": "",
        "ServiceID": "_nomad-task-3c6891c4-f8db-ea07-0ee1-ce7cac6df9f3-frontend-httpbin-http",
        "ServiceName": "httpbin",
        "ServiceTags": [
            "http"
        ],
        "ServiceAddress": "10.0.0.2",
        "ServiceTaggedAddresses": {
            "lan_ipv4": {
                "Address": "10.0.0.2",
                "Port": 31973
            },
            "wan_ipv4": {
                "Address": "10.0.0.2",
                "Port": 31973
            }
        },
        "ServiceWeights": {
            "Passing": 1,
            "Warning": 1
        },
        "ServiceMeta": {
            "external-source": "nomad"
        },
        "ServicePort": 31973,
        "ServiceSocketPath": "",
        "ServiceEnableTagOverride": false,
        "ServiceProxy": {
            "Mode": "",
            "MeshGateway": {},
            "Expose": {}
        },
        "ServiceConnect": {},
        "CreateIndex": 5582,
        "ModifyIndex": 5582
    },
    {
        "ID": "5d5c41c2-b65a-3855-4119-102e0e72a765",
        "Node": "ip-10-0-0-2",
        "Address": "10.0.0.2",
        "Datacenter": "eu-west-1",
        "TaggedAddresses": null,
        "NodeMeta": null,
        "ServiceKind": "",
        "ServiceID": "_nomad-task-62558968-f06f-06ac-fdf2-341b57b6fbcd-frontend-httpbin-http",
        "ServiceName": "httpbin",
        "ServiceTags": [
            "http"
        ],
        "ServiceAddress": "10.0.0.2",
        "ServiceTaggedAddresses": {
            "lan_ipv4": {
                "Address": "10.0.0.2",
                "Port": 30874
            },
            "wan_ipv4": {
                "Address": "10.0.0.2",
                "Port": 30874
            }
        },
        "ServiceWeights": {
            "Passing": 1,
            "Warning": 1
        },
        "ServiceMeta": {
            "external-source": "nomad"
        },
        "ServicePort": 30874,
        "ServiceSocketPath": "",
        "ServiceEnableTagOverride": false,
        "ServiceProxy": {
            "Mode": "",
            "MeshGateway": {},
            "Expose": {}
        },
        "ServiceConnect": {},
        "CreateIndex": 5583,
        "ModifyIndex": 5583
    }
]

[Rutul_Shah]

The json response you have attached is of consul catalog API response. I am talking about the API definition json. If you read Josh’s answer, Josh had asked to add the transform block in front of query definition. I am not getting where exactly that block needs to be added. If you can show a sample example that would be helpful

[Olu]

@Rutul_Shah

If you read Josh’s answer, Josh had asked to add the transform block in front of query definition

I am not sure I can see this. Can you help point this out?

If you meant this:

@Jameso

“service_discovery”: {
“use_discovery_service”: true,
“query_endpoint”: “http://10.0.0.4:8500/v1/catalog/service/httpbin ”,
“use_nested_query”: false,
“parent_data_path”: “”,
“data_path”: “Address”,
“port_data_path”: “ServicePort”,
“target_path”: “”,
“use_target_list”: true,
“cache_timeout”: 20,
“endpoint_returns_list”: true
}

Then the full API definition is shared on the 11th post

@Jameso

please find api doc here : https://sharetext.me/vbyppvdfum

[Jameso]

So for me the trick was to set up a second api in tyk, this api will point at the service mesh service catlog endpoint. Then add a transformer to this api amd use the template above in the response transformation.

Then in your first api tell it to use this new service catalog endpoint instead.

This should do the trick for you.

[Rutul_Shah]

Check 15th post/message

[Rutul_Shah]

Jameso , Can you share your API json for reference?