Open Amoratinos opened 1 year ago
Any updates on this? We really need this too!
We are thinking of achieving this using URL schemes like grpc://
and grpcs://
in the server URL instead.
The scheme will override the TLS setting (๐ icon).
Let me know if that unblocks your use case.
Correct me if I'm wrong, this approach does not work just yet. This would unblock our case!
+1 on this issue since it's blocking many developers working with grpc since mostly local dev is using non TLS and production is using TLS. thanks!
+1
This will be great to achieving this using URL schemes like grpc:// and grpcs:// in the server URL instead. The scheme will override the TLS setting (๐ icon).
Details: We also have gRPC Service running on 2 environments - local machine and dev in cloud For local env I send gRPC queries with TLS Disabled. For dev cloud env i send gRPC queries with TLS Enabled. I have 100 scripts Each time I run all the scripts and switch from Local to DEV/Cloud environment I need to manually Disable Enable for each request! I do not want to DUPLICATE my collection and to keep the LOCAL and DEV environments version. I want to be able to Enable/Disable TLS from script.
Is there an existing request for this feature?
Is your feature request related to a problem?
Among different environment TLS settings can be different, e.g. Local development vs QA. As we use server reflection to trigger requests when we switch between different environments users have to be aware that they have to click on the ๐ icon to change TLS settings.
Describe the solution you'd like
I'd like that TLS settings for gRPC requests could be enabled/disabled based on an environment setting.
Describe alternatives you've considered
No response
Additional context
No response