Skip to content

Commit 3c208e2

Browse files
lbroudouxlbroudoux
committed
Initial import of project
Signed-off-by: Laurent Broudoux <[email protected]>
1 parent 6062494 commit 3c208e2

File tree

15 files changed

+2801
-0
lines changed

15 files changed

+2801
-0
lines changed

‎.github/workflows/build-verify.yml‎

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
name: build-verify-package
2+
on:
3+
push:
4+
paths-ignore:
5+
- '.github/**'
6+
- '.gitignore'
7+
- 'ADOPTERS*'
8+
- 'LICENSE'
9+
- 'README*'
10+
- 'CHANGELOG*'
11+
- 'ROADMAP*'
12+
- 'GOVERNANCE*'
13+
pull_request:
14+
paths-ignore:
15+
- '.github/**'
16+
- '.gitignore'
17+
- 'ADOPTERS*'
18+
- 'LICENSE'
19+
- 'README*'
20+
- 'CHANGELOG*'
21+
- 'ROADMAP*'
22+
- 'GOVERNANCE*'
23+
permissions: read-all
24+
jobs:
25+
build-verify-package:
26+
runs-on: ubuntu-latest
27+
environment: Build
28+
steps:
29+
- name: Checkout Code
30+
uses: actions/checkout@v4
31+
32+
- name: Set up JDK 17 for x64
33+
uses: actions/setup-java@v4
34+
with:
35+
java-version: '17'
36+
distribution: 'temurin'
37+
architecture: x64
38+
cache: maven
39+
40+
- name: Build Java components
41+
run: mvn -B clean package
42+
43+
- name: Verify Javadoc completion
44+
run: mvn -B javadoc:javadoc

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

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
name: Manage stale issues and PRs
2+
3+
on:
4+
schedule:
5+
- cron: "0 0 * * *"
6+
7+
permissions:
8+
contents: read
9+
10+
jobs:
11+
stale:
12+
permissions:
13+
issues: write # for actions/stale to close stale issues
14+
pull-requests: write # for actions/stale to close stale PRs
15+
if: startsWith(github.repository, 'microcks/')
16+
name: Mark issue or PR as stale
17+
runs-on: ubuntu-latest
18+
steps:
19+
- uses: actions/stale@99b6c709598e2b0d0841cd037aaf1ba07a4410bd #v5.2.0 but pointing to commit for security reasons
20+
with:
21+
repo-token: ${{ secrets.GITHUB_TOKEN }}
22+
stale-issue-message: |
23+
This issue has been automatically marked as stale because it has not had recent activity :sleeping:
24+
25+
It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.
26+
27+
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).
28+
29+
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.
30+
31+
Thank you for your patience :heart:
32+
stale-pr-message: |
33+
This pull request has been automatically marked as stale because it has not had recent activity :sleeping:
34+
35+
It will be closed in 30 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation.
36+
37+
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).
38+
39+
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.
40+
41+
Thank you for your patience :heart:
42+
days-before-stale: 30
43+
days-before-close: 30
44+
stale-issue-label: stale
45+
stale-pr-label: stale
46+
exempt-issue-labels: keep-open
47+
exempt-pr-labels: keep-open
48+
close-issue-reason: not_planned

‎.github/workflows/welcome-new-users.yml‎

Lines changed: 73 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,73 @@
1+
# Welcome new users by creating a comment in the first time issue/PR.
2+
# Adding a friendly message in the comment to tip non-stargazers to star our repo.
3+
#
4+
# Props to https://github.com/wow-actions/welcome
5+
6+
name: Welcome New Users with Thanks and Tip non-stargazers ;-)
7+
on:
8+
pull_request_target:
9+
types: [opened, closed]
10+
issues:
11+
types: [opened]
12+
permissions:
13+
contents: read
14+
jobs:
15+
run:
16+
permissions:
17+
issues: write # for wow-actions/welcome to comment on issues
18+
pull-requests: write # wow-actions/welcome to comment on PRs
19+
# Do not run on bots and maintainers
20+
if: ${{ !contains(fromJson('["dependabot[bot]", "dependabot-preview[bot]", "allcontributors[bot]"]'), github.actor) }}
21+
runs-on: ubuntu-latest
22+
steps:
23+
#- uses: wow-actions/welcome@v1
24+
- uses: wow-actions/welcome@72817eb31cda1de60f51893d80e2e82ce57f7e76 # To pin v1.3.0
25+
with:
26+
# GitHub token as default GITHUB_TOKEN
27+
28+
FIRST_ISSUE_REACTIONS: '+1, hooray, rocket, heart'
29+
30+
FIRST_ISSUE: |
31+
👋 @{{ author }}
32+
33+
Welcome to the Microcks community! 💖
34+
35+
Thanks and congrats 🎉 for opening your first issue here! Be sure to follow the issue template or please update it accordingly.
36+
37+
📢 If you're using Microcks in your organization, please [add your company name to this list](https://github.com/microcks/.github/blob/main/ADOPTERS.md). 🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.
38+
39+
If you need to know why and how to add yourself to the list, please read the blog post ["Join the Microcks Adopters list and Empower the vibrant open source Community 🙌"](https://microcks.io/blog/join-adopters-list/)
40+
41+
Hope you have a great time there!
42+
43+
FIRST_PR_REACTIONS: '+1, hooray, rocket, heart'
44+
45+
FIRST_PR: |
46+
👋 @{{ author }}
47+
48+
Welcome to the Microcks community! 💖
49+
50+
Thanks and congrats 🎉 for opening your first pull request here! Be sure to follow the pull request template or please update it accordingly.
51+
52+
Hope you have a great time there!
53+
54+
FIRST_PR_MERGED: |
55+
🎉 @{{ author }}
56+
57+
You are now a Microcks community contributor! 💖
58+
59+
Thanks and congrats 🚀 on merging your first pull request! We are delighted and very proud of you! 👏
60+
61+
📢 If you're using Microcks in your organization, please [add your company name to this list](https://github.com/microcks/.github/blob/main/ADOPTERS.md). 🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.
62+
63+
If you need to know why and how to add yourself to the list, please read the blog post ["Join the Microcks Adopters list and Empower the vibrant open source Community 🙌"](https://microcks.io/blog/join-adopters-list/)
64+
65+
Kudos and please keep going, we need you 🙌
66+
67+
STAR_MESSAGE: |
68+
🌟 ~~~~~~~~~ 🌟
69+
70+
📢 If you like Microcks, please ⭐ star ⭐ our repo to support it!
71+
72+
🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.
73+

‎ADOPTERS.md‎

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
# Adopters
2+
3+
**📢 _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._**
4+
5+
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 🙌"
6+
7+
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:
8+
- Please don't include your organization's logo or other trademarked material
9+
- Add a reference (link to a public blog post, video, slides, etc) mentioning that Microcks is used
10+
11+
> You can also contact the project [maintainers](https://github.com/microcks/.github/blob/main/MAINTAINERS.md) if you have any questions or need further information.
12+
13+
14+
| Organization | Contact | Description of Use / Reference |
15+
|-----------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
16+
| [Lombard Odier Group](https://www.lombardodier.com/) | [Ludovic Pourrat](https://github.com/ludovic-pourrat) | Multi-protocol API Mocking and Sandbox as a service #APIOps
17+
| [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) ⭐️
18+
| [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
19+
| [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/) ⭐️
20+
| [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).
21+
| [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) ⭐️
22+
| [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
23+
| [sesam-vitale](https://www.sesam-vitale.fr/) | [Vincent Fasciaux](mailto:[email protected]) | We use Microcks to replace the SUT's dependencies with test doubles in order to accelerate our API deliveries
24+
| [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.
25+
| [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.
26+
| [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.
27+
| [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.
28+
| [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.
29+
| [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.
30+
| [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.
31+
| [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.
32+
| [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).
33+
| [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!

‎CHANGELOG.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
# CHANGELOG
2+
3+
## Introduction
4+
5+
This file provides a high-level summary of the changes and updates made to the Microcks Java Client project.
6+
7+
## Releases
8+
9+
For a comprehensive list of changes, please visit the [official release page](https://github.com/microcks/microcks-java-client/releases)
10+
11+
## For More Information
12+
13+
For more detailed release notes, please refer to the [Microcks blog page](https://microcks.io/blog/).

‎CODE_OF_CONDUCT.md‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
# Microcks Community Code of Conduct
2+
3+
Microcks project follows the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md).
4+
5+
## Our Pledge
6+
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
7+
8+
## Enforcement
9+
10+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team via [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

0 commit comments

Comments
 (0)