Merge branch 'master' of https://github.com/microcks/microcks-ansible…

…-operator

.github/workflows/build-verify.yml

@@ -5,7 +5,7 @@ on:
       #- '.github/**'
       - '.gitignore'
       - 'LICENSE'
-      - 'README*'
+      - '*.md'
 jobs:
   build-verify-package:
     runs-on: ubuntu-latest
@@ -78,4 +78,4 @@ jobs:
             --file build/Dockerfile \
             --label "org.opencontainers.image.revision=${GITHUB_SHA}" \
             --label "org.opencontainers.image.created=${{ steps.date.outputs.date }}" \
-            --tag=quay.io/microcks/microcks-ansible-operator:$IMAGE_TAG .
+            --tag=quay.io/microcks/microcks-ansible-operator:$IMAGE_TAG .

.github/workflows/stale-issues-prs.yml

@@ -0,0 +1,49 @@
+# This workflow is used to manage stale issues and PRs in the Microcks project.
+name: Manage stale issues and PRs
+
+on:
+  schedule:
+    - cron: "0 0 * * *"
+
+permissions:
+  contents: read
+
+jobs:
+  stale:
+    permissions:
+      issues: write  # for actions/stale to close stale issues
+      pull-requests: write  # for actions/stale to close stale PRs
+    if: startsWith(github.repository, 'microcks/')
+    name: Mark issue or PR as stale
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@28ca1036281a5e5922ead5184a1bbf96e5fc984e # To pin v9.0.0 
+        with:
+          repo-token: ${{ secrets.GITHUB_TOKEN }}
+          stale-issue-message: |
+            This issue has been automatically marked as stale because it has not had recent activity :sleeping:
+            
+            It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. 
+            
+            There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under [open governance model](https://github.com/microcks/.github/blob/main/CODE_OF_CONDUCT.md). 
+            
+            Let us figure out together how to push this issue forward. Connect with us through [one of many communication channels](https://microcks.io/community/) we established here.
+            
+            Thank you for your patience :heart:
+          stale-pr-message: |
+            This pull request has been automatically marked as stale because it has not had recent activity :sleeping:
+            
+            It will be closed in 30 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation.
+            
+            There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under [open governance model](https://github.com/microcks/.github/blob/main/CODE_OF_CONDUCT.md). 
+            
+            Let us figure out together how to push this pull request forward. Connect with us through [one of many communication channels](https://microcks.io/community/) we established here.
+            
+            Thank you for your patience :heart:
+          days-before-stale: 30
+          days-before-close: 30
+          stale-issue-label: stale
+          stale-pr-label: stale
+          exempt-issue-labels: keep-open
+          exempt-pr-labels: keep-open
+          close-issue-reason: not_planned

ADOPTERS.md

@@ -0,0 +1,38 @@
+# Adopters
+
+**📢 _If you're using Microcks in your organization, please add your company name to this list. 🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact._**
+
+Respect is a core principle in our open source community, see our [Code of Conduct](https://github.com/microcks/.github/blob/main/CODE_OF_CONDUCT.md). We value your contributions, rely on your input, and believe that together we can achieve more.
+
+If you need to know why and how to add yourself to the list, please read the blog post "[Join the Microcks Adopters list](https://microcks.io/blog/join-adopters-list/) and Empower the vibrant open source Community 🙌"
+
+This document also lists the organizations that use Microcks based on public information available in blog posts, events and videos. If any organization would like to get added or removed please edit this file (make a pull request) after following our [contribution guide](https://github.com/microcks/.github/blob/master/CONTRIBUTING.md) and by following these specifics guidelines:
+- Kindly include a reference (such as a link to a public blog post, video, slides, etc.) that mentions the use of Microcks.
+- You consent to having your company’s name and logo featured on the [Microcks.io website](https://microcks.io/), included in our adopters' section, and potentially displayed in our rotating logo carousel.
+
+> You can contact the project [maintainers](https://github.com/microcks/.github/blob/main/MAINTAINERS.md) if you have any questions or need further information.
+
+
+| Organization                                                                | Contact                                                                                                                                                                                                                                                          | Description of Use / Reference                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+|-----------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| [Lombard Odier Group](https://www.lombardodier.com/) | [Ludovic Pourrat](https://github.com/ludovic-pourrat) | Multi-protocol API Mocking and Sandbox as a service #APIOps
+| [Lombard Odier Group](https://www.lombardodier.com/) | [Ludovic Pourrat](https://github.com/ludovic-pourrat) | APIdays Paris 2022 - Adding a mock as a service capability to your API strategy portfolio 👉 [slide deck](https://speakerdeck.com/apidays/apidays-paris-2022-adding-a-mock-as-a-service-capability-to-your-api-strategy-portfolio-ludovic-pourrat-lombard-odier) ⭐️                                                               
+| [La Poste Groupe](https://www.lapostegroupe.com/) | [Nicolas Matelot](https://www.linkedin.com/in/nicolas-matelot/) [Romain Gil](https://www.linkedin.com/in/romain-gil-8444898a) | Cloud-native application development, API Mocking and Sandbox 
+| [J.B. Hunt](https://www.jbhunt.com/) | [Carol Gschwend](https://github.com/carolgschwend) |  Accelerating cloud-native application development "The developers of the project mentioned above saved at least 7 months using Microcks. They were not only able to work concurrently but also captured the exact business requirements specified by the product owner in the form of example request/response pairs. These persistent mocks can now be utilized in sandbox environments if needed." See J.B. Hunt ⭐️ [blog post](https://microcks.io/blog/jb-hunt-mock-it-till-you-make-it/) ⭐️       
+| [Société Générale](https://www.societegenerale.com/en) | [Patrice Lachance](https://github.com/patlachance) | Multi-protocol API Mocking, Testing and Sandbox for cloud-native APIs / applications. Integrated in [Cloud Innovation Platform](https://github.com/societe-generale/cloud-innovation-platform).                         
+| [Société Générale](https://www.societegenerale.com/en) | [Patrice Lachance](https://github.com/patlachance) | Cloud Innovation Platform presentation and Microcks demo 👉 [Red Hat Summit 2019](https://www.redhat.com/files/summit/session-assets/2019/T8B6B4.pdf) ⭐️      
+| [Deloitte](https://www.deloitte.com/global/en.html) | [Madiha Rehman](https://www.linkedin.com/in/madihar/) | Utilised Microcks to create backend mocks for 170+ APIs including REST and SOAP services
+| [sesam-vitale](https://www.sesam-vitale.fr/) | [Vincent Fasciaux](mailto:vincent.fasciaux@sesam-vitale.fr) | We use Microcks to replace the SUT's dependencies with test doubles in order to accelerate our API deliveries
+| [BNP PARIBAS](https://group.bnpparibas/en/) | [Nadji BERRAF](https://www.linkedin.com/in/nadji-berraf-26707148/) | We use Microcks since 2022 to mock our legacy core banking systems and mainframe APIs in order to increase agility, accelerate development, and reduce costs. Microcks is also integrated into our API-first strategy for building and delivering new cloud-native services.
+| [Akwatype](https://akwatype.io) | [Pierre-Michel Bret](https://www.linkedin.com/in/pierre-michel-bret/) | Use of Microcks to mock the APIs corresponding to the OpenAPI contracts generated by Akwatype, integration through Git.
+| [codecentric AG](https://www.codecentric.de) | [Daniel Kocot](https://www.linkedin.com/in/danielkocot/) | API Operations pipeline with an integration of Microcks and consulting services around API Mocking and Testing.
+| [CNAM](https://www.ameli.fr) | [Sébastien Fraigneau](https://www.linkedin.com/in/s%C3%A9bastien-fraigneau-82826a2) | Using Microcks to mock SOAP services for the French healthcare system. REST is coming.
+| [API Quality](https://apiquality.io/en/) | [Omar del Valle](https://www.linkedin.com/in/omardelvalle/)| We are using Microcks for a step of the API first cycle.
+| [CloudAPPi](https://cloudappi.net) | [Marco Antonio Sanz Molina Prados](https://www.linkedin.com/in/marco-antonio-sanz-molina-prados-09733518/)| We manage over 40 APIs strategies in medium and big companies and install Microcks as a mock server.
+| [Sypid](https://www.sypid.com/) | [Zubair Aslam](https://www.linkedin.com/in/zubes1/)| Sypid consultants are highly experienced in the Spec-first approach to API and integration design. We use Microcks to implement this approach effectively. We found the docker extension is specifically useful to get started quickly.
+| [Inetum Software](https://www.inetum.com/) | [Jérôme Palon](https://www.linkedin.com/in/jpalon/)| We use Microcks as an API centralisation and mock server for the social and civil security division, paving the path for migration to microservices and event-driven cloud architecture.
+| [Fluent CI](https://fluentci.io/) | [Tsiry Sandratraina](https://github.com/tsirysndr)| We use Microcks to mock and test our REST and GraphQL APIs. We also provide an open source [Microcks module](https://github.com/fluent-ci-templates/microcks-pipeline) for [Dagger](https://dagger.io) and [Fluent CI](https://fluentci.io).
+| [Nordic Semiconductor](https://nordicsemi.com) | [Patrick Barnes](https://www.linkedin.com/in/patrick-barnes-pdx/) | We use Microcks mainly via testcontainers to test the REST APIs (and probably soon, our async, event-based APIs) for the microservices that comprise our IoT platform, [nRFCloud.com](https://nrfcloud.com/). Microcks has been invaluable, and the Microcks team a real pleasure to work with!
+| [Office national de l'emploi (ONEm)](https://www.onem.be/) | [Samuel Antoine](https://www.linkedin.com/in/samuel-antoine-07347b171/) [Christophe Lopez](https://www.linkedin.com/in/aeoncl/) | We use Microcks as both OpenAPI contract testing tool and mock provider.
+| [Bitso](https://bitso.com/) | [Caio Amaral](https://www.linkedin.com/in/camaral) | Microcks supports Bitso's integration and capacity testing infrastructure, allowing us to isolate the applications through well defined gRPC contracts. 
+| [Catena Clearing](https://catenaclearing.io/) | [Andre Sionek](https://www.linkedin.com/in/andresionek) | We use Microcks to mock 3rd party APIs so we can develop against them without hitting the real endpoints, Microcks is also used to run integration tests. 

BACKERS.md

@@ -0,0 +1,46 @@
+# Sponsors & Backers
+
+[Microcks](https://microcks.io/) is a [Cloud Native Computing Foundation Sandbox](https://landscape.cncf.io/?selected=microcks) project 🚀 with its ongoing development made possible entirely by the support of the awesome sponsors and backers listed in this file. If you'd like to join them, please consider [sponsoring](https://opencollective.com/microcks) Microcks's development.
+
+**BTW 📢 _If you're using Microcks in your organization, please add your company name to the adopters list. 🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact._**
+https://github.com/microcks/.github/blob/main/ADOPTERS.md
+
+> Platinum💎, gold🥇 and silver🥈 **sponsors**, [join us](https://opencollective.com/microcks) 🙌<br>
+> **Invest** in **your supply chain!**
+
+If you run a business and is using Microcks in a revenue-generating product/service, it would make business sense to sponsor Microcks development: it ensures the project that you rely on a healthy, strong and engaged community. It can also help your exposure in the open source community and makes it easier to attract new talents.
+
+If you'd like to help and support Microcks to [level up](https://www.cncf.io/project-metrics/) within the [CNCF](https://www.cncf.io) and keep growing the open source way, please consider:
+
+- [Become a backer or sponsor on OpenCollective](https://opencollective.com/microcks).
+
+## Special Sponsors
+[image width="350"]: #
+<p align="center">
+  <a href="https://postman.com/"><img src="https://voyager.postman.com/logo/postman-logo-orange.svg" alt="Postman logo" width="350"></a>
+</p>
+
+## Platinum Sponsors
+[image width="300"]: #
+[Become the first platinum sponsor](https://opencollective.com/microcks/contribute/platinum-sponsors-61341/checkout?interval=month&amount=2000&name=&legalName=&email=)
+
+## Gold Sponsors
+[image width="250"]: #
+[Become the first gold sponsor](hhttps://opencollective.com/microcks/contribute/gold-sponsors-61340/checkout?interval=month&amount=1000&name=&legalName=&email=)
+
+## Silver Sponsors
+[image width="200"]: #
+[Become the first silver sponsor](https://opencollective.com/microcks/contribute/silver-sponsors-61339/checkout?interval=month&amount=500&name=&legalName=&email=)
+
+## Bronze Sponsors
+[image width="150"]: #
+<p align="center">
+  <a href="https://bitso.com/"><img src="https://logowik.com/content/uploads/images/bitso5417.jpg" alt="Bitso logo" width="120"></a>
+  <a href="https://www.devmark.ai/fern/?utm_source=microcks&utm_loc=readme&utm_type=logo"><img src="https://uploads-ssl.webflow.com/64f77a831b9d50c279dc926c/6568d0303c2a1435c108e114_fern.svg" alt="Fern logo" width="150"></a>
+</p>
+
+[Become a bronze sponsor](https://opencollective.com/microcks/contribute/bronze-sponsors-61338/checkout?interval=month&amount=100&name=&legalName=&email=)
+
+## OpenCollective Generous Backers
+
+<a href="https://opencollective.com/microcks#section-contributors" target="_blank"><img src="https://opencollective.com/microcks/backers.svg?width=800"></a>

CHANGELOG.md

@@ -0,0 +1,17 @@
+# CHANGELOG
+
+## Introduction
+
+This file provides a high-level summary of the changes and updates made to the Microcks project.
+
+## Releases
+
+For a comprehensive list of changes, please visit the [official release page](https://github.com/microcks/microcks/releases) 
+
+## For More Information
+
+For more detailed release notes, please refer to the [Microcks blog page](https://microcks.io/blog/).
+
+## For specific changes on this repo
+
+Refer to the [activity view](https://docs.github.com/en/repositories/viewing-activity-and-data-for-your-repository/using-the-activity-view-to-see-changes-to-a-repository) of the current repository for detailed information on all recent changes.