-
Notifications
You must be signed in to change notification settings - Fork 468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apollo Server cannot fetch operation manifest, permission denied #996
Comments
Hey @jhalborg, thanks for submitting an issue! I was actually running through this workflow yesterday and ran into the same problem. For now, there's a small catch when you first introduce the plugin to your server. You have to publish the schema one more time with See the docs here for more details. Sorry about the trouble! Either way, let me know if this solves the problem for you. |
Hey @trevor-scheer - Thanks for getting back to me, and sorry for the late reply. I'll give it a go ASAP, but it's been moved down our priorities list until #994 is addressed as well, because until then we can't really use the operation registry anyway, as we rely heavily on tag use |
@trevor-scheer - Finally got time to circle around to this just now, and this issue seems to indeed have been resolved by pushing the service again. However, now I'm blocked by this issue instead 😣 😄 |
My mistake - I still get the same error after downgrading to
Our server instantiation:
|
@jhalborg Could you try re-publishing your schema with the latest version of the |
Correction: The |
@abernix - Same result.
After that,
I noticed another version, |
Ping @abernix :) Do you, Apollo, deem that the Registry is ready for production use? I've met a handful of issues just when trying to get started following the tutorials, and the plugin is still in |
@jhalborg Sorry for the problems and delays in response! (It may be easier to debug this through Intercom support within Apollo Engine. 😄) That said, we do have many using it in production and we do plan on graduating it to a non- Your output from |
@jhalborg is this still an ongoing issue for you? Our new iteration of the operation manifest should resolve this issue altogether. You can find our migration docs here: https://www.apollographql.com/docs/platform/operation-registry/#migrating-from-01-alpha4-to-020-alpha1 I'm going to close this for now, but feel free to reopen if the issue persists after upgrading. Thanks again! |
@trevor-scheer I am still facing this issue. |
@sanketCactus can you please provide a runnable reproduction? |
Intended outcome:
Following the quickstart from the docs will allow the server to fetch operations from the registry
Actual outcome:
I get the following error on server startup:
in spite of having correctly pass the Engine API key. I've double and triple checked the key, and it works correctly with other services (i.e. tracing).
How to reproduce the issue:
Follow the quickstart, see the error
Versions
The text was updated successfully, but these errors were encountered: