Wrong Microcks CLI executable configured in spring-boot-order-service
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 50/100
Research direction
Open shift-left-demo/spring-boot-order-service/microcks-docker-compose.yml and inspect lines 10-17. Update the Microcks CLI executable and option there, then verify the compose configuration uses the names specified in the issue.
Written by the indexing model from the issue text.
Description
Describe the bug
The docker-compose file for spring-boot-order-service is referencing an incorrect Microcks CLI executable and option.
the executable is defined as microcks-cli, but the correct executable name is microcks.
Additionally, the CLI option --insecure is not valid and must be replaced with --insecure-tls.
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Microcks version or git rev
No response
Install method (docker-compose, helm chart, operator, docker-desktop extension,...)
No response
Additional information
No response
- Dominant language
- HTML
- Stars
- 42
- Forks
- 30
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stephrobert/dsoxlab#238 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sublimehq/package_control#1779 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nwg-piotr/nwg-displays#145 ·
-
Bob Shell support Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100