Closed jenschude closed 6 years ago
Hi,
Thank you for the issue report. Can you please run the following command in your shell and report back the result?
$ npm list -g api-console-builder
$ npm list -g api-console-builder
/usr/local/lib
└─┬ api-console-cli@0.2.1
└── api-console-builder@0.4.0
Do you get this warning message when running the command?
Warning: You are trying to use local RAML file as an input but the --use-json optionis not set.
Users won't be able to access the RAML file. The CLI will use --use-json to generate a JSON file for build.
Never mind. I was able to reproduce it already.
Thanks!
@jayS-de So the issue is with the latest release.
CLI downloads information about latest release if specific tag is not passed as an option.
The source downloader don't actually care about version number of downloaded console and yesterday there was new release of old version v3.x
. So the builder is trying to build the old console which is not possible.
As a workaround I suggest to use -t
option to use specific release:
$ api-console build ./api.raml -o build -t v4.0.0
I'll fix it in coming days.
Ah kay. So I will add this to my build script and Dockerfile.
Would be nice to use also only stable tags for the build instead of master by default.
Agree. Thanks for letting me know.
When using api-console-cli version 0.2.x I'm getting following error:
Using following RAML file:
With v0.1.4 I don't have this issue.