Team,
I was trying to implement Virtual endpoint through API Definition but sample provided in it is referring to building Custom Middleware.
# API Definitions
An API Definition describes the configuration of an API. It instructs Tyk Gateway how to configure the API.
To check the supported features of the API Definitions CRD version you're currently using, please use the "Switch branches / tags" feature on GitHub and select corresponding version tag.
## Implemented Capabilities / Support Status
| Symbol | Description |
|--------|-----------------------------------|
| ✅ | Fully supported |
| ⚠️ | Untested / Requires Documentation |
| ❌️ | Not currently supported |
## API Types
| Type | Support | Supported From | Comments | Sample |
|--------------------------------|---------|----------------|------------------------------|--------------------------------------------------------------------------------------------|
| HTTP | ✅ | v0.1 | - | |
| HTTPS | ✅ | v0.4 | - | [Sample](./../config/samples/tls/example.yaml)️ |
| TCP | ✅ | v0.1 | - | |
This file has been truncated. show original
API definition hyberlink takes me to tyk-operator/custom_plugin.md at master · TykTechnologies/tyk-operator · GitHub
Can you help with the valid example for virtual endpoint configuration?
Gregor
April 28, 2021, 2:55pm
2
Hi @SaravananPeriyasamy , the approach is the same for custom middleware and virtual endpoints. the gateway essentially treats the virtual endpoint as middleware that is invoked when the endpoint is called.
Thanks,
G