api-management
Here are 172 public repositories matching this topic...
-
Updated
Jul 6, 2022 - Go
-
Updated
Jul 1, 2022 - JavaScript
Description
- When I am using APISIX_PROFILE, if a value is assigned, it will be displayed as follows
a. config-dp.yaml
b. config-cp.yaml
c. ...[others]
- However, when I don't do the assignment, I expect to be
config.yaml, but I actually getconfig-.yaml. - It works fine, but the file names look ugly. As someone with code cleanliness, it's hard to accept i
On contexts with many APIs and APIs calling other APIs in chains, having too many spans in the zipkin/jaeger dashboards may lead to a too complex usage of such dashboards and of not necessary big data volumes.
For Tyk's admin team, the steps representing the time spent in each Tyk middleware are much valuable.
But the upstream APIs teams just want to know the global time spent in Tyk interna
-
Updated
Jul 6, 2022 - PHP
Please describe your use case / problem.
A user reports that they're getting timeouts of the apiserver trying to talk to apiext
Error from server: error when creating "STDIN": conversion webhook for getambassador.io/v3alpha1, Kind=Host failed: Post https://emissary-apiext.emissary-system.svc:443/webhooks/crd-convert?timeout=30s: net/http: TLS handshake timeout
despite the apiext supposedl
Gloo Edge Version
1.12.x (beta)
Kubernetes Version
No response
Describe the bug
add https://github.com/golangci/golangci-lint to ci
Steps to reproduce the bug
unknown bugs likely in code due to unhandled errors
Expected Behavior
ci should fail when we have obvious code errors
Additional Context
No response
-
Updated
May 4, 2022
-
Updated
Jun 10, 2022 - JavaScript
-
Updated
Jul 6, 2022 - Ruby
-
Updated
Jul 6, 2022 - Java
-
Updated
Nov 5, 2019 - JavaScript
-
Updated
Jun 21, 2022 - PHP
-
Updated
Mar 11, 2021 - JavaScript
-
Updated
Jan 10, 2022 - JavaScript
-
Updated
Jan 14, 2018 - Java
See https://github.com/apiman/apiman/blob/master/.github/workflows/verify.yaml
Might as well also add builds for Java 11 and 15 while at it.
Follow up on #1245
Add a check to validate that x-extensible-enum properties have a string type.
Feature request
Please describe your feature
We currently support OpenAPI3 data import support, which is based on the DataLoader interface. The DataLoader interface provides good support for extending our new data import and exporters.
However, it is difficult for us to handle the following scenario, when users have multiple environments, such as three environments like development
Describe your problem(s)
In the "Complexity Analysis" tab in GraphQL try-out page in devportal, we can see only the complexity Values of each field. If we want to know the complexity value or the depth value, we have to calculate ourself manually. Instead, it would be a nice to have feature to have the possibility to display the calculated complexity/depth values on a button click. So before
-
Updated
Jun 27, 2022 - Java
-
Updated
Jul 6, 2022 - Go
-
Updated
Jun 22, 2022 - Kotlin
Alpine Linux is affected by a serious security CVE-2022-28391 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28391
The AlpineLinux Release Note https://alpinelinux.org/posts/Alpine-3.12.12-3.13.10-3.14.6-3.15.4-released.html
We should update the currently used Alpine Linux image version.
Describe the issue
The connection from sdk to server is plug-in,
see #com.tencent.tsf.femas.governance.config.impl.ServerConnectorConfigImpl,
The current practice is http connection polling the data form femas server, We want to support grpc protocol to improve performance
Lack of unit tests
-
Updated
Jul 7, 2022 - TypeScript
-
Updated
Jun 28, 2022 - Vue
-
Updated
Jul 6, 2022 - Scala
-
Updated
Oct 27, 2020 - Go
API management apps
Mockend
On-demand GraphQL & REST fake API
Moesif API Insights
Understand API usage and take action with user-centric API observability
Improve this page
Add a description, image, and links to the api-management topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the api-management topic, visit your repo's landing page and select "manage topics."
expected result:
example.com?param=abc -> will become example.com
example.com/?param=abc -> will stay example.com/
actual result:
example.com?param=abc -> become example.com
example.com/?param=abc -> stays example.com/?param=abc