Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Subworkflow conversion expects to be run in examples (0/2) #213

Closed
potiuk opened this issue May 22, 2019 · 0 comments
Closed

Subworkflow conversion expects to be run in examples (0/2) #213

potiuk opened this issue May 22, 2019 · 0 comments
Labels
bug Something isn't working nice-to-have Nice to have - not needed for the initial implementation

Comments

@potiuk
Copy link
Collaborator

potiuk commented May 22, 2019

Describe the bug
Conversion of configuration with subworkflow does not work in "installed" version of o2a. It expects the sub-workflow to be in "examples" folder and when there are no sources it fails to find the subworkflow.

To Reproduce

Steps to reproduce the behavior:

  1. Install o2a with pip install o2a in a fresh virtualenv outside of the sources
  2. Run conversion o2a -i <YOUR_PATH>/oozie-to-airflow/examples/demo -o /tmp/out
  3. It fails trying to find sub-workflow and failing.

Expected behaviour
We should work out a way to pass information on where the subworkflows are when processing a workflow that has sub-workflow.

@potiuk potiuk added the bug Something isn't working label May 22, 2019
@potiuk potiuk changed the title Subworkflow conversion expects to be run in examples Subworkflow conversion expects to be run in examples (0/2) May 24, 2019
@potiuk potiuk added this to the Delta milestone May 24, 2019
@potiuk potiuk added the nice-to-have Nice to have - not needed for the initial implementation label Jun 28, 2019
@potiuk potiuk removed this from the Delta (nice-to-have time permitting) milestone Jul 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working nice-to-have Nice to have - not needed for the initial implementation
Projects
None yet
Development

No branches or pull requests

2 participants