Microcks

Microcks is a cloud native, open source tool under CNCF for API and microservices mocking and testing. This project focuses on creating a validated and repeatable SaaS architecture for deploying Microcks on AWS, with the ultimate goal of listing it on the AWS Marketplace through the AWS Partner Network Co-Sell program. By addressing the community's frequent demand, this initiative will simplify Microcks' adoption while leveraging a complete suite of AWS services to ensure scalability, security, and ease of deployment. The core Microcks maintainers focus on features, security, and enhancements. The adopters are responsible for production setups. However, a shared repository of best practices can help users learn from one another in a true open-source spirit. Participants will contribute to the Microcks community repository by documenting the AWS Marketplace deployment. Expected Outcome: Enable Microcks adopters to confidently deploy production-ready setups on AWS, ensuring the scalability and reliability needed for enterprise environments. By integrating Microcks into the AWS Marketplace, the project will further enhance its visibility and adoption within the AWS ecosystem. - Designing and validating a SaaS architecture that is compliant with AWS Foundational Technical Review (FTR). - Utilizing AWS-native services such as EKS, Aurora (PostgreSQL), DocumentDB, API Gateway, IAM, and CloudFormation for an end-to-end deployment. - Streamlined deployment workflows

Microcks (https://microcks.io/) is a cloud native, open source tool under CNCF for API and microservices mocking and testing. This project seeks to enhance our CLI tool by integrating frameworks like Cobra CLI. Expected Outcome: @JulienBreux has started some work on creating a utility tool called `mksctl` here (https://github.com/JulienBreux/mksctl). The base of `mksctl` has also been reversed into the `1.x` branch of the `microcks-cli` repo (https://github.com/microcks/microcks-cli/tree/1.x). The main goals of a new CLI version are: - Provide the same interface for exiting test and import commands - Provide a way to easily install this tool via integration with packet manager (brew, apt or others) - Allow developers to easily start new Microcks instances with mksctl start and mksctl stop, for example - Allows quick addition of new commands like import from URL, import all the files from a directory, create job, list jobs, and so on. Moving to standard tools like Cobra CLI is a way to make it more scalable so that people can contribute and add the features they want.

Microcks (https://microcks.io/) is a cloud native, open source tool under CNCF for API and microservices mocking and testing. This project aims to enhance the [Microcks Hub](https://hub.microcks.io/) by updating the existing sandbox environment or adding new hub entries to mock key APIs IT industry leaders use. The goal is to make it easier for developers to test and prototype integrations with popular APIs like GitHub, Twilio, Stripe, or Salesforce using Microcks. Expected Outcome: Participants can choose to focus on one or both of the following aspects: 1. Update and Refresh the Existing Sandbox: - Improve the sandbox environment provided by Microcks Hub for existing mock APIs. - Ensure compliance with the latest versions of existing APIs. - Enhance documentation, usability, and deployment mechanisms. 2. Add New Hub Entries for Key Industry APIs: - Develop mock entries for leading APIs like GitHub, Twilio, Stripe, or Salesforce, but we welcome any ideas... - Ensure the mocks cover essential endpoints and realistic request-response pairs. - Provide detailed examples and use cases to support integration testing.

Microcks (https://microcks.io/) is a cloud native, open source tool under CNCF for API and microservices mocking and testing. Microcks Hub (https://hub.microcks.io) is a community-driven hub that aggregates standards or product-related API mocks and test suites. Microcks hub was created a long time ago with a technology stack we should refresh (Angular 8 at the moment). Expected Outcome: - refresh UI aligned with ongoing work and decisions taken for the main Microcks UI, see: https://github.com/orgs/microcks/discussions/1458 - It was initially designed to be deployable only in a single public instance, but there are requests to make it deployable on-premises. - We're looking for contributions on this part, such as helping develop Docker Compose files, Kubernetes Helm Charts, or whatever makes sense. - The code base is hosted on https://github.com/microcks/hub.microcks.io

<p>The Microcks CLI (microcks-cli, written in Go) is a key part of Microcks' CI/CD story - it lets developers trigger contract tests and import artifacts from the command line and in GitHub Actions. This project goes into the developer experience layer. Today, developers must navigate to the Microcks web UI in a browser to see test results, check mock status, and diagnose import errors. There is no IDE integration, no offline validation mode, and no way to get mock results inline with the code being tested. This project builds three focused improvements that bring Microcks into the editor and the local dev loop: a VS Code extension, a local dry-run mode powered by Testcontainers, and an updated GitHub Actions output format that annotates PRs with per-operation pass/fail results.</p><p><br></p><p>Expected Outcome:</p><p>&nbsp;- A VS Code extension (microcks-vscode) published to the VS Code Marketplace that connects to a running Microcks instance and shows: loaded services, mock operation status, recent test run results, and importer job logs - all inline in the editor sidebar (Like postman, thunder client)</p><p>&nbsp;- A microcks test --dry-run flag in the CLI that uses Testcontainers (the Microcks uber image) to spin up an ephemeral local Microcks instance, import the specified artifact, run the contract test, report results, and tear down - with no external Microcks server required</p><p>&nbsp;- A demo video and documentation page on microcks.io showing the full local-to-CI workflow</p><p><br></p>