You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to use Prism as a service mock in Bitbucket pipelines, but have not been successful.
docker-compose:
services:
apimock:
# Locking to 4.10.3 due to open issue in prism with 4.10.4 - https://github.com/stoplightio/prism/issues/2138
image: stoplight/prism:4.10.3
platform: linux/amd64
command: 'mock -h 0.0.0.0 /tmp/api.json'
volumes:
- ./docker/apiv2mock/api.json:/tmp/api.json:ro
ports:
# Serve mocked API locally on port 8999
- '8999:4010'
I have tried using script and running various commands in bitbucket-pipelines.yml:
No success with several iterations of volumes and script. The result is always:
prism <command>
Commands:
prism mock <document> Start a mock server with the given document file
prism proxy <document> <upstream> Start a proxy server with the given document file
Options:
--version Show version number [boolean]
--help Show help [boolean]
Which seems to indicate that it's using the default ENTRYPOINT of prism.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I would like to use Prism as a service mock in Bitbucket pipelines, but have not been successful.
docker-compose:
I have tried using script and running various commands in bitbucket-pipelines.yml:
No success with several iterations of volumes and script. The result is always:
Which seems to indicate that it's using the default ENTRYPOINT of
prism
.Beta Was this translation helpful? Give feedback.
All reactions