itowlson

The config in `spin@unversioned` is the old Spin 1 config interface. `wasi-config` is at https://github.com/fermyon/spin/tree/main/wit/deps/wasi-runtime-config-2024-09-27 (note the snapshot package name because the upstream repo doesn't identify revs yet).

Regarding the proposed `--disallowed-outbound-hosts`: If a component says it needs `*://example.com:8080`, and this is disallowed, that should be a "can't satisfy requirements" failure, caught at validation time, correct? If a...

@rylev This is great! I particularly appreciate your emphasis on granularity, that we get a clear message "you broke SDK 1.3" rather than "`test_http_go_works` failed" One tiny thought: it may...

There's a limited amount we can do on the Draft side about this; is it something we should tackle on the Helm side, or just try to recognise the error...

This seems like it could break a lot of people's muscle memory - is there a strong reason for removing it?

Without telemetry, it's hard to say how prevalent that muscle memory would be. My removal plan would be: 1. Switch docs over to use `up --build` and wait (for people...

@dicej are you best placed to look at this?

Looks like there's a smol challenge here. A Redis application _requires_ an `application.trigger.redis.address` entry. When we create a _new_ `spin.toml` file (`spin new`), we can safely prompt for that and...

(Incidentally this would have been a challenge for HTTP too had wise Lann not wisely made `base` optional, the wise fellow.)

My _guess_ is that the thought behind the order was that a user writing `SPIN_VARIABLE_DB_ADDR=foo spin up` should get the behaviour they (thought they) asked for, even if another provider...