wgc router compose: Could not introspect subgraph

[vidmartin]

Component(s)

cli

Component version

0.72.0

wgc version

0.72.0

controlplane version

no controlplane

router version

0.137.1

What happened?

Description

The wgc router compose command started saying Could not introspect subgraph for all our subgraphs (hosted in Google Cloud Run / Functions), even though it worked before (we've been using it for a very long time without much issues). I tried wgc versions 0.53.3, 0.62.2 and 0.72.0 (on Windows) and all of them gave the error. I suspect it has something to do with the year turning from 2024 to 2025, because it worked in December 2024 (wgc router compose is part of our deployment pipeline and the deployment in December was successful). The subgraphs use https, but the error persists even with NODE_TLS_REJECT_UNAUTHORIZED=0. When testing it against a subgraph hosted on localhost, it works, even with https.

Steps to Reproduce

I don't know.

Expected Result

wgc router compose producing the router config successfuly.

Actual Result

Could not introspect subgraph error message.

Environment information

Environment

OS: Windows 11 (but it was also failing in our GitLab pipeline, where we use some Linux image)
Package Manager: npm

Router configuration

Router execution config

Log output

Additional context

I don't think this issue has anything to do with the particular subgraph SDLs.

[github-actions]

WunderGraph commits fully to Open Source and we want to make sure that we can help you as fast as possible.
The roadmap is driven by our customers and we have to prioritize issues that are important to them.
You can influence the priority by becoming a customer. Please contact us here.

[vidmartin]

We solved it, it was an authorization error on our side - the authorization token we were using to in the introspection config for wgc router compose was not valid anymore. But this wasn't clear from the output of wgc router compose. When we queried query { _service { sdl } } to our subgraph manually, it was clear from the response that it was an authorization issue.