Just like the Connection, we want to support many types of DataSets. E.g. a MySQL DataSet, an S3 DataSet, etc. However, each of these will need to define different fields. An S3 DataSet would need to define the file bucket, while the MySQL DataSet would need to define the MySQL schema and table.
To ensure the fields are not a complete free form, KubeETL supports the DataSetType. With the DataSetType we can perform dynamic validation on the DataSet in a validating webhook. See the ConnectionValidatingWebhook for an example on how to implement this.
Just like the Connection, we want to support many types of DataSets. E.g. a MySQL DataSet, an S3 DataSet, etc. However, each of these will need to define different fields. An S3 DataSet would need to define the file bucket, while the MySQL DataSet would need to define the MySQL schema and table.
To ensure the fields are not a complete free form, KubeETL supports the DataSetType. With the DataSetType we can perform dynamic validation on the DataSet in a validating webhook. See the ConnectionValidatingWebhook for an example on how to implement this.