Closed gmambro closed 2 years ago
I think this issue was introduced with https://github.com/backstage/mkdocs-techdocs-core/commit/ddd8d28547e1ec6eb3dcd05b019c21307d45bc53
Changing the line
theme_override = config["theme"].copy()
to
theme_override = config["theme"]
locally seemed to fix things, but I'm not enough of a python/techdocs expert to know if that is a safe thing to do
As a sidenote, I have seen this pipeline error a few times before as well:
caused by unknown error 'Command mkdocs failed, exit code: 1'
Which is obviously not very helpful. Is there any way to bubble the real mkdocs error up? So it's easier to tell if it's a logic error like this
Hey folks! Thanks for your patience, and for reporting.
Just released v1.1.1
with a very narrow fix (and added a workflow to run unit tests that will hopefully help reduce issues like this cropping up again in the future). We have end-to-end tests in the main Backstage monorepo that started failing after 1.1.0
, which are now passing again after releasing 1.1.1
. So I'm confident bumping will resolve the issue for you!
If you happen to rely on the theme override capabilities introduced in v1.1.0
, those may still not be working 100%, but at least the docs generation is working again.
...Is there any way to bubble the real mkdocs error up? So it's easier to tell if it's a logic error like this
@rmanny great point! My guess is that the TechDocs CLI likely treats things differently compared with the log output in Backstage frontend (if you've got it configured to run that way). An issue in the main Backstage monorepo with that detail (whether it's TechDocs CLI or the Backstage UI) would be a good first step.
Hello,
my pipeline stopped working as soon as started using 1.1.0.
my mkdocs.yml looks like this
Reverting to 1.0.2 solved the problem