Support TLS in Redis trigger (`rediss://` scheme) about spin HOT 6 OPEN

From Discord discussion I think @seungjin's priority is the Redis trigger, but we should allow it on the outbound Redis API too (including a suitable default port for allowed_outbound_hosts?).

from spin.

Actually it works well with publishing messages to Redis with rediss:// in spim.toml

allowed_outbound_hosts = [
    "redis://{{ redis_host }}:{{ redis_port }}",
    "rediss://{{ redis_host }}:{{ redis_port }}",
]

With above, I can publish and can see messages were being passed with redis-cli.

The problem is trigger. Trigger is not getting from rediss://

[application.trigger.redis]
address = "rediss://{{ redis_credential }}@{{ redis_host }}:{{ redis_port }}"

redis trigger with rediss:// never triggered.

This is currently NOT high priority - but good to have (ATM).

from spin.

@seungjin Locally or on fermyon's cloud ? For me locally it's working fine on secured redis endpoint.

from spin.

ref #999

from spin.

@radu-matei #999 only covers outbound - from comments above it looks like the trigger is the problem (although evidently working for some folks). I'll update the issue title.

from spin.

I think the ask here is for the ability to create clients with user-provided TLS certs for client-side authentication or even provide a different ca root certificate instead of the system default.

from spin.