Great work on the tool, it will let us remove a few pounds of CICD scripts.
Listing some feedback here (as advised by Jan Inge).
Will you supply patterns or guidance for structuring the custom modules. Do you have any thoughts on which level a project should group their artifacts into a module.
Is there a plan for added support for the development lifecycle, e.g. downloading a full solution as configuration (from existing project), download buttons on other resources than transformation (e.g. datasets).
It would perhaps be better to let the RAW config support multiple tables (one per DB), one file per table seems a bit bloated. A “Download CLI” on the DB level would also be great.
Is it possible to have the auth verify command also check transformation credentials?
Not directly related to the tool, but it seems to be a mismatch between tranformation credentials configuration in the UI and via the tool. We cannot configure the advanced scenario in the UI, and we cannot verify the auth via the tool. This means that we cannot verify the transformation credentials before we have done a deployment.
The transformation schedule active flag isn't respected on deployment.
It is an option to put the query in the transformation yaml - but if you do, the build step gives a warning of a missing sql file. Also, the file with the query should perhaps have the 'sparql' or 'rq' extension, since it isn't ANSI SQL? This causes some editors to show that these files contains errors.