We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We horizontally scale our backstage backend servers on k8s.
grpc-playground works in two steps.
/proto-info/:entity
/send-request/:entity
now if there are two pods backstage backend, first call can go to first pod, and second call can go to second pods, and cause missing proto error.
Is there a way to solve this by having a common source for .proto files, say like GCS/S3 bucket.
The text was updated successfully, but these errors were encountered:
Thanks. This plugin should support backstage discovery feature
Please try configuring AWS S3 discovery along with this configuration guideline and report if it works
Sorry, something went wrong.
No branches or pull requests
We horizontally scale our backstage backend servers on k8s.
grpc-playground works in two steps.
/proto-info/:entity
endpoint. where the proto definition is copied to local file./send-request/:entity
where the actual call is made.now if there are two pods backstage backend, first call can go to first pod, and second call can go to second pods, and cause missing proto error.
Is there a way to solve this by having a common source for .proto files, say like GCS/S3 bucket.
The text was updated successfully, but these errors were encountered: