microcks / microcks/api-lifecycle
Wrong Microcks CLI executable configured in spring-boot-order-service
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 42
- Forks
- 30
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 4
Description
### Describe the bug
The docker-compose file for spring-boot-order-service is referencing an incorrect Microcks CLI executable and option.
https://github.com/microcks/api-lifecycle/blob/5c679213d3615f61822b73d43b045ec3fe7de6ef/shift-left-demo/spring-boot-order-service/microcks-docker-compose.yml#L10-L17
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_
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.
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.
Assessment
- Tech stack
- docker-compose
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 50/100