Open bhanurz opened 2 years ago
@stewartbryson Hello, please check the above feature request and attached PR for proposed changes. Thank you.
I've been traveling the last 2 weeks... sorry for the delay.
I'm curious... have you tested passing the full path to the file to --pipeline-dir
? I believe that actually works. If so, perhaps just a rename of --pipeline-dir
would be the better choice here. Just trying to simplify. It's a breaking change, so maybe that is something to consider as well.
@stewartbryson Hello. We tried with pipeline-dir but it does not work and returns an error that reports that a directory path is expected. Also note that it is not a breaking change as we are not changing the behaviour of existing options rather we are adding a new option that let's us point to a specific file relative to pipeline-dir.
PR is merged. Please test and close this issue if it’s working. Thanks a bunch for the contribution.
Is your feature request related to a problem? Please describe. We use gradle-confluent for in our CI/CD. We often come across scenarios where we want to execute a single file rather than all files under a directory.
Describe the solution you'd like If there was a pipeline-file parameter to specify a particular file in the pipeline directory, then it would allow us specify required file. Example:
This would read following file for execution:
Note that adding new param is backward compatible.
Describe alternatives you've considered Alternative solution was to put every file in a directory so we can specify the wrapper directory if we wanted to execute a single file. This was not a clean solution so we did not go ahead with this.
Additional context Proposed changes: https://github.com/RedPillAnalytics/gradle-confluent/pull/121