fix(types): warn on unknown interface

[brooksmtownsend]

Feature or Problem

This PR downgrades the unrecognized interface error into a warning as inspired by some of the recent additions to keyvalue like batch and watch. We want to maintain a balance in validation to make sure that users don't accidentally link on, say, wasi:keyvalue/atormics, but we don't completely block the addition of new interfaces e.g. in wasmcloud:[email protected]

Open to thoughts here.

Related Issues

Release Information

Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

[lxfontes]

Our interface map is not the authoritative source of all valid interfaces, but hey it is pretty good!

I wonder if this is where --force comes in.
The safest path is to fail on any validation error, even warnings. Ex:

wash app deploy newish-interface.yaml
Warning: Unknown interface "bla"
exit 1

vs

wash app deploy --force newish-interface.yaml
Warning: Unknown interface "bla"
exit 0

[brooksmtownsend]

I like that idea @lxfontes , I think we should fail on warnings and then allow forcing past that. My thought is that we should still fail without allowing a --force on the actual errors, e.g. an invalid manifest or a link to a component that doesn't exist. Do you think a --force should override all of that or still have some failure cases?

[lxfontes]

agreed 👍 --force should only bypass warnings