devtoAPISpec
apiclarity
devtoAPISpec | apiclarity | |
---|---|---|
1 | 9 | |
0 | 483 | |
- | 1.7% | |
10.0 | 3.0 | |
over 1 year ago | 26 days ago | |
Go | ||
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
devtoAPISpec
-
Risk scoring your API Specification with Panoptica
1: From the Panoptica Dashboard select APIs from the menu. Here you will see all the workload APIs running in the Kubernetes cluster. Double-click on the front-end workload and you will be taken to the API inventory page. Here we will see details once we upload the API Spec. 2: Download the API spec files from Github. Go to (https://github.com/rami000/devtoAPISpec) and download the repo to your local desktop. 3: Extract the file. In the api-spec directory there are 4 JSON files. We will upload the frontend.json file to the Panoptica UI 4: Go back into the Panoptica UI. Make sure you are in APIs > Internal APIs > front-end. From this page select the SPECS tab. Click on Upload a spec and upload the frontend.json file and click Finish – this may take a while.
apiclarity
-
Two approaches to make your APIs more secure
We'll install APIClarity into a Kubernetes cluster to test our API documentation. We're using a Kind cluster for demonstration purposes. Of course, if you have another Kubernetes cluster up and running elsewhere, all steps also work there.
-
How to Get Started with Open Source
If you go to APIClarity, the first thing you’ll see is the source code (Figure 1), followed by some documentation at the bottom.
-
Risk scoring your API Specification with Panoptica
This feature is available in the open-source tool APIClarity, as part of the OpenClarity initiative.
-
Show HN: Mitmproxy2swagger – Automagically reverse-engineer REST APIs
Hi, I would also like to add another tool I'm contributing to at work (cisco) called APIClarity [1]. It aims at reconstructing swagger specifications of REST microservices running in K8S, but can also be run locally.
This is a challenging task and we don't support OpenAPI v3 specs yet (we are working on it).
Feel free to have a look, and get ideas from it :)
We'll also be presenting it at next Kubecon 2022.
[1]: https://github.com/openclarity/apiclarity
- Microservices API challenges
-
How to Use OpenAPI for Secure and Robust API Integration
For example, APIClarity is a tool that observes all of the API traffic within your Kubernetes environment. Based on traffic observation, APIClarity infers an OpenAPI description for those APIs. This is especially helpful if the API creator never defined or provided such a description. It also surfaces potential problems with existing APIs, such as requests made to undocumented, shadow APIs or continued use of deprecated, zombie APIs. If you’re getting started on the path toward OAS compliance, then tools like APIClarity can be a great source of insight and observability.
-
Watching the Requests Go By: Reconstructing an API Spec with APIClarity
The fundamental first step to solving this problem is to create an API spec and use it to audit and document the APIs your apps use. Ideally, we would create an API spec simply by observing API traffic in real-world applications. In the past, there was no simple, scalable, and open-source tooling capable of doing this. Now, we have APIClarity—an open-source API traffic visibility tool for Kubernetes (K8s) clusters. It’s purpose-built to address the gap and enable API reconstruction through observation.
- Reconstruct Open API Specifications from real-time workload traffic seamlessly
What are some alternatives?
oasdiff - OpenAPI Diff and Breaking Changes
Nacos - an easy-to-use dynamic service discovery, configuration and service management platform for building cloud native applications.
api-firewall - Fast and light-weight API proxy firewall for request and response validation by OpenAPI specs.
microservices-demo - Deployment scripts & config for Sock Shop
kusk - CLI for Kusk Gateway related functionality
openapi-preprocessor - An authoring tool for OpenAPI specifications
meshery - Meshery, the cloud native manager
RESTest - RESTest: Automated Black-Box Testing of RESTful Web APIs
layer5 - Layer5, expect more from your infrastructure
swagger-ui - Swagger UI is a collection of HTML, JavaScript, and CSS assets that dynamically generate beautiful documentation from a Swagger-compliant API.
openapi-to-fastapi - OpenAPI 3.0 to FastAPI route generator
cnfuzz - Breaking Cloud Native Web APIs in their natural habitat.