This is the second and final PR related to this issue: #193
This PR builds the interface users interact with to choose whether or not they want to output .flow/.project files or .job/.properties files. As stated in my prior PR (#196) the default is .job/.properties for now.
After this PR is merged (and subsequently released), users can specify that they want to output yaml by adding:
generateYamlOutput true or
generateYamlOutput()
in the hadoop closure within their gradle files.
The change to existing code to make this happen is only ~75 lines, the other 500 lines added are from adding 4 end-to-end tests that confirm basic functionality for Flow 2.0. These tests mirror those done on the Azkaban side to confirm proper uploading.
This is the second and final PR related to this issue: #193
This PR builds the interface users interact with to choose whether or not they want to output .flow/.project files or .job/.properties files. As stated in my prior PR (#196) the default is .job/.properties for now.
After this PR is merged (and subsequently released), users can specify that they want to output yaml by adding:
generateYamlOutput true
orgenerateYamlOutput()
in the hadoop closure within their gradle files.
The change to existing code to make this happen is only ~75 lines, the other 500 lines added are from adding 4 end-to-end tests that confirm basic functionality for Flow 2.0. These tests mirror those done on the Azkaban side to confirm proper uploading.