Move orka config validation to config package
What does this MR do?
Two commits:
- Moves the config validation to the config package.
- Avoids unnecessary copying of config fields into provider fields.
Why was this MR needed?
This validation was polluting the provider package and this moves into the direction of having a dedicated validation layer.
What's the best way to test this MR?
TestValidation
is mostly a copy of the previous TestNew
. TestNew
now has less focus on just config validation.
What are the relevant issue numbers?
Closes #88 (closed)
Edited by Arran Walker