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]

This trait should be a link trait, just because that's where the source_config value lives

[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