feat(validation): validation fails if component has source_config

[markkovari]

Feature or Problem

Related Issues

#288

Release Information

Consumer Impact

Testing

Unit Test(s)

unit tests should cover the negative case, other validation calls don't have this error

Acceptance or Integration

Manual Verification

[markkovari]

I do have 2 questions tho:

• is it even a valid configuration, if not feel free to point out edge cases to add
• the validation looks similar to a callback hell, hopefully you have wide enough screens, please call me out if it needs refactor (update: definitely needs to be refactored, I forgot how to rust 😿 )

Appreciate

[brooksmtownsend]

Hey @markkovari ! I think the structure of this PR looks great, you may just need to consider a change or two after #307. If we want to try and move this forward now, we should at least just change the parsing of the source_config key to be in a link trait

[brooksmtownsend]

Alright @markkovari you should be good to proceed with this one 😄 Just take note of the newer structure where the source block is the recommended route, and source_config is a backwards compatible field. I would recommend just validating that the source: config: block isn't present, since we want to deprecate source_config out in a future release anyways

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this has been closed too eagerly, please feel free to tag a maintainer so we can keep working on the issue. Thank you for contributing to wasmCloud!

[markkovari]

Just a question here: since v0.13.0 the fields are deprecated (source_config) and (target_config), this is still relevant right?
Currently the yaml parsing into the structure is always None so it is doable by the casual yaml traversing/parsing method.
And this should be even related to this too:
wasmCloud/wasmCloud#2862