-
Notifications
You must be signed in to change notification settings - Fork 249
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
Outbound connectivity to databases is allow-all by default #897
Comments
We need to define how this is going to work though. The set of allowed HTTP hosts is currently fixed in the This may be moot right now when we don't have a full concept of channels, but I don't want to casually bake this into (There were some good discussions a while back around decoupling policy - set by operators - from application building. Might be time to reassess the roadmap on that.) |
Yes, I think this is a better long-term approach ("labels" + runtime config), though we'll still need to support existing non-labels interfaces for the time being. |
We need this for:
We also need to consider moving to the unified |
Yes it would be! |
The rust, go and .net SDKs support outbound connections to Redis and Postgres (not go).
Unlike outbound http connections, these are allow-all by default, e.g. you can call any host from the component using this feature.
We should stick to deny-all and implement the functionality similar to http-outbound, where the configuration need to specify which hosts you're allowed to call.
The text was updated successfully, but these errors were encountered: